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.
+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.