On Wed, Jun 01, 2011 at 12:21:15 -0400, Richard Hipp wrote: > On Wed, Jun 1, 2011 at 12:19 PM, Stephan Beal <sgb...@googlemail.com> wrote: > > > On Wed, Jun 1, 2011 at 5:18 AM, Don Ireland <sql...@donireland.com> wrote: > > > > > GenBookMRU_3 TEXT, GenBookMRU_4 TEXT); > > > > > > > i might be very wrong here, but i SEEM to remember that having a semicolon > > on the end of a line sent to sqlite3_exec() (or similar) doesn't work. i > > might, however, be mis-remembering from a session with the MySQL or ocilib > > (Oracle) APIs. > > > > I think you are probably remembering a MySQL or Oracle episode. SQLite is > very tolerant of semicolons in sqlite3_exec(). You can put multiple > semicolons before and/or after the SQL statement and it should still work.
More than that. sqlite3_exec will happily accept *multiple* statements separated with semicolons and execute *all* of them. In contrast to sqlite3_prepare(_v2), which will prepare only the first one (but still accept the string). -- Jan 'Bulb' Hudec <b...@ucw.cz> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users