| Subject: | Better diagnostics in sqlt-diff |
I run into two situations where sqlt-diff could give better diagnostics:
$ sqlt-diff /tmp/1.sql /tmp/2.sql
Unknown argument '/tmp/1.sql'
...
This should maybe tell that the parser specification is missing:
Cannot parse argument '/tmp/1.sql', parser specification is missing.
If one of the SQL files is missing a trailing semicolon after the create
table statement, then the output is just:
ERROR (line 1): Invalid statement: Was expecting comment, or use, or
set, or drop, or create, or alter, or insert, or
delimiter, or empty statement
Maybe the error message should be extended to note that the semicolon is
probably missing. Or even the parser changed to allow missing semicolons
(DBI for instance usually does not need the trailing semicolon).
Regards,
Slaven