| Summary: | One off report | ||
|---|---|---|---|
| Product: | Koha | Reporter: | TLamanna <tlamannajr> |
| Component: | Reports | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | david.roberts |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
TLamanna
2018-04-27 19:00:08 UTC
How do you foresee handling any errors in the SQL? I know I usually have to have at least 2 goes at getting the SQL in my reports correct because I usually have a typo somewhere. If you run it once, and it then disappears because it isn't saved, do you really want to have to start again from the beginning? |