Skip Menu |
 

This queue is for tickets about the SQL-Translator CPAN distribution.

Report information
The Basics
Id: 33771
Status: new
Priority: 0/
Queue: SQL-Translator

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.09000
Fixed in: (no value)



Subject: Better diagnostics in sqlt-diff
MIME-Version: 1.0
X-Mailer: MIME-tools 5.418 (Entity 5.418)
Content-Type: text/plain
Charset: utf8
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 831
Download (untitled) / with headers
text/plain 831b
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


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.