Alexander Kanavin <alex.kana...@gmail.com> writes: > These two are orthogonal. "amalgamation" is building sqlite from a > single source file for performance and simplicity reasons, which is > what yocto does as well, despite there being no mention of it in the > recipe. Enabling or disabling specific sqlite features can be done > regardless of whether amalgamation or original source code file bunch > is in use. > > Alex >
This is true for most features, but not necessarily for SQLITE_ENABLE_UPDATE_DELETE_LIMIT. Since said feature affects the supported SQL syntax (e.g. "DELETE FROM foo LIMIT 1" results in a parse error without the extension) the parser needs to be configured & generated to support this. The amalgamated version contains a preconfigured parser, which may or may not have been configured with SQLITE_ENABLE_UPDATE_DELETE_LIMIT. See https://www.sqlite.org/howtocompile.html#building_the_amalgamation for details. So the presence of the feature in the amalgamated sqlite3.c really depends how the file was generated in the first place. Cheers, Henrik > 2018-09-12 16:54 GMT+02:00 Brian Hutchinson <b.hutch...@gmail.com>: >> I need to enable SQLITE_ENABLE_UPDATE_DELETE_LIMIT and while >> researching how >> to do that I read the "amalgamation" needs to be rebuilt. Sqlite >> site gives >> instructions on how to do that but I was wondering if this is really >> necessary in a yocto environment. I did some searches in recipies >> and the >> work directory where sqlite3 was built and do not get any hits at >> all on >> "amalgamation". >> >> Any words of wisdom? I never heard of sqlite amalgamation or had to >> deal >> with it before so this is a new one on me. >> >> Regards, >> >> Brian >> >> -- >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >> -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
