Timeline for MySQL Stored Procedure Compiles Without Error (I want the error to occur)
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2020 at 14:06 | comment | added | user309223 | [... You can't find such error like false columns, mysql will only find syntax errors. ...] Thanks for this. | |
| Jun 10, 2020 at 22:17 | comment | added | nbk | no it helps to find certain errors. You can't find such error like false columns, mysql will only find syntax errors. that is why stired procedures need help often help. And for that is needed the data processed. sql is not that hard. you have a result in mind and then you build layer after lyer to get to teh result. Storred procedured functions give you more "normal" methods of programming nd enhance so sql | |
| Jun 10, 2020 at 20:56 | comment | added | user309223 | Thanks for the answer. My example in original question has misspelled column name which the Stored Procedure Editor cleanly accepts without showing error message when I hit "Apply". So it appears the misspelled column name does not constitute a "syntax error". Secondly, correct me if this is wrong, the "SIGNAL" statement you linked above seems to engage only if I execute the procedure which defeats my purpose. I would like the error message when I hit "Apply" button if possible. Thoughts? | |
| Jun 10, 2020 at 20:37 | history | answered | nbk | CC BY-SA 4.0 |