Agreed that the MySQL error reporter is primitive, and that 'lint for
MySQL' would be a smash hit, but if you look up error 1064 you'll find
it is a naming error, two of which are visible in your error
report--column names enclosed in double quotes.
Hugh Sasse wrote:
>I'm fairly new to MySQL and am getting an error messages like:
>ERROR 1064 (42000) at line 5: You have an error in your SQL syntax;
>check the manual that corresponds to your MySQL server version for
>the right syntax to use near '"id" int(14) unsigned NOT NULL auto_increment,
> "forename" varchar(40) NOT NU' at line 2
>neelix hgs 18 %>
>So it doesn't tell me exactly where, or what the nature of the
>syntax error is (and it can't even tell me it is version 4.1.13
>which I know already). It has truncated the second line, so it's not
>that the rest is missing. My editor's syntax highlighter doesn't
>show anything awful. This is actually for lines 7 and 8 of the
>input, the first 4 lines being comments, so the numbering in the
>output is wrong.
>Are there any tools (like lint for C) to be more verbose and helpful
> Thank you,
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.11.14/131 - Release Date: 10/12/2005