On Mon, Jul 06, 2009 at 01:22:52PM -0400, Andy Froncioni scratched on the wall: > > On 6-Jul-09, at 1:20 PM, D. Richard Hipp wrote: > > At http://www.sqlite.org/compile.html under section 1.6, it says you > > cannot use SQLITE_OMIT_ compile-time options with the amalgamation. > > The documentation never says you cannot use > > SQLITE_ENABLE_UPDATE_DELETE_LIMIT with the amalgamation, but it > > should, since SQLITE_ENABLE_ is really just SQLITE_OMIT_ with the > > default behavior inverted, and so SQLITE_ENABLE_ will not work with > > the amalgamation for exactly the same reason that SQLITE_OMIT_ will > > not. > > See? That's how I read this, too. Oh, well... I've wasted more time > on stupider things than this, so it's no use cying over spilled > milk. :-)
This, at least, seems pretty clear: http://sqlite.org/compile.html#enable_update_delete_limit SQLITE_ENABLE_UPDATE_DELETE_LIMIT This option enables an optional ORDER BY and LIMIT clause on UPDATE and DELETE statements. If this option is defined, then it must also be defined when using the 'lemon' tool to generate a parse.c file. Because of this, this option may only be used when the library is built from source, not from the amalgamation or from the collection of pre-packaged C files provided for non-Unix like platforms on the website. -j -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Our opponent is an alien starship packed with atomic bombs. We have a protractor." "I'll go home and see if I can scrounge up a ruler and a piece of string." --from Anathem by Neal Stephenson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
