Tab, >> file). Anyway, it can't help to try the following: >> C:\mysql\bin>>mysql --max-allowed-packet=32M < \dev_hotel_data.sql
> Thanks, I'll try that... But in the meantime, is there something I can > do to get Mysql to show me more information about the syntax error? I > think that the difference in the parser might be causing my line-numbers > to be off. I went into my text editor and replaced the line that had > the "error" with a blank line, and when I ran it again it still reported > the same error on the same line #...So I'm wondering if there's a better > way to get Mysql to give me more clues as to which line is causing the > error. Nope. But, as I said, it doesn't look like it's a "real" syntax error. Something (maybe due to the communications buffer size) sends only part of that last INSERT command to MySQL, and that's what results in an error. Regards, -- Stefan Hinz <[EMAIL PROTECTED]> iConnect GmbH <http://iConnect.de> Heesestr. 6, 12169 Berlin (Germany) Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3 [filter fodder: sql, mysql, query] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
