|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
- [mojo-dev] [jira] (MSQL-87) Lookup error - conflict ... Steve Schols (JIRA)
- [mojo-dev] [jira] (MSQL-87) Lookup error - conf... Steve Schols (JIRA)
- [mojo-dev] [jira] (MSQL-87) Lookup error - conf... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MSQL-87) Lookup error - conf... Robert Scholte (JIRA)
- [mojo-dev] [jira] (MSQL-87) Lookup error - conf... Steve Schols (JIRA)
- [mojo-dev] [jira] (MSQL-87) Lookup error - conf... Robert Scholte (JIRA)

A colleague of mine has found what might cause this issue.
Apparently, when ending every statement with a semicolon ';', the script will effectively throw database errors.
When (any / all) statements don't end with a semicolon ';', the script will ignore any error and just stop executing the script in the middle of it, when an error occurs.
Without announcing the error and terminating, the next script is just executed.
Ofcourse, every statement should ideally end with a semicolon, but in many of our large scripts, this appears not to be the case.
Can this be checked out and/or fixed?