Summary: | Update and Run SQL button should save changes even if report fails to run | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Reports | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | barbara.johnson, blawlor, bugzilla, cj.lynce, ddaghita, george, kebliss, nick |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 23824 | ||
Bug Blocks: |
Description
Andrew Fuerste-Henry
2023-12-29 17:36:29 UTC
+1 +1 as well This bug continues to cause me to lose work when I mistakenly click "Update and Run" while testing new queries. If my changes have introduced an error, all changes are lost. While I suppose the ultimate answer here is to get so gud at SQL that I don't make mistakes, that may take some time. I'd love to be able to use this button in the meantime. Is this still a bug? I tested on main and 23.05, but I was only able to reproduce this behavior if I used the browser's back button. Even then it only displays the original query, but the updated one with the error is actually saved in the database. I see that a nice thing to know in case you ever wanted to revert to the query with no error, you could click the browser's back button and copy and paste the query and save it again. After using the update and run button and getting an error, if you use the Koha interface the to return to editing the query you will see the edited query: - clicking on the name of the report in the breadcrumbs - selecting edit from the edit dropdown - using the 'return to previous page' link in the error message |