Hi, just to clarify: it is sqlite, not the sqlite driver which does not support newlines in SQL statements. Some other SQL engines like MySQL do support newlines, so this appears to be a design decision (I don't know what the standard says). To verify, use these SQL scripts:
----- select version() ----- and ----- select sqlite_version() ----- write the scripts to a file using Unix line endings, and pipe them into mysql and sqlite, respectively. The former succeeds, whereas the latter complains about incomplete SQL. I think it is easier to avoid newlines on the input side rather than trying to "fix" sqlite's behaviour in the driver. regards, Markus Quoting Kris Groves <[EMAIL PROTECTED]>: > The parsing of the sql statement will fail at the first new line char as > this indicates the end of the c-string. > > This is the first time I have seen newline characters explicitly > embedded in an sql statement. Is there a reason that the newline > characters are needed ? -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ libdbi-users mailing list libdbi-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libdbi-users
