Bug 35672 - Update and Run SQL button should save changes even if report fails to run
Summary: Update and Run SQL button should save changes even if report fails to run
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Reports (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 23824
Blocks:
  Show dependency treegraph
 
Reported: 2023-12-29 17:36 UTC by Andrew Fuerste-Henry
Modified: 2024-03-07 18:31 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2023-12-29 17:36:29 UTC
To recreate:
- have a report that works, example "SELECT 1+1"
- edit your report to have a SQL error, example "SELECT 1 plus 1"
- click Update and Run SQL, get an error message due to SQL error
- click to edit report again, confirm none of your changes were saved
- re-edit your report to contain the SQL error
- click Update, confirm your report saves with an error

When using Update and Run, we should save the SQL even if it has an error, just as we do with the old Update button.
Comment 1 George Williams (NEKLS) 2024-01-03 17:28:59 UTC
+1
Comment 2 Barbara Johnson 2024-01-03 17:33:39 UTC
+1 as well
Comment 3 Andrew Fuerste-Henry 2024-02-28 18:39:50 UTC
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.