On Dec 1, 2009, at 12:17 PM, Ralf Junker wrote:
>
> always made me believe that all options to omit features are
> supported.
> Now I am not sure which ones I can really trust.
>
> Could you clear up my confusion?
>
There are several dozen individual compile-time options. We obviously
On 01.12.2009 18:35, Jay A. Kreibich wrote:
> Important Note: The SQLITE_OMIT_* compile-time options are
> unsupported.
Oops! Thanks for focusing my eyes - they tend to skip introductions and
move right to the details.
Now having that read, let me point out that in spite of the statement
the
On Tue, Dec 01, 2009 at 06:17:49PM +0100, Ralf Junker scratched on the wall:
> Reading
>
>http://www.sqlite.org/compile.html
>
> always made me believe that all options to omit features are supported.
Read closer:
1.6 Options To Omit Features
...
Important Note: The
On 01.12.2009 18:05, D. Richard Hipp wrote:
> The key point to bare in mind here is that SQLITE_OMIT_SUBQUERY is
> not a supported compile-time option. None of the major users of
> SQLite make use of SQLITE_OMIT_SUBQUERY. We do not test it. And it
> appears that it is broken in the current
On Dec 1, 2009, at 11:53 AM, Ralf Junker wrote:
> Compiling with SQLITE_OMIT_SUBQUERY, sqlite3ExprCodeIN() is compiled
> out
> but at the same time still required at other places in expr.c.
>
> As such, expr.c does not link well with SQLITE_OMIT_SUBQUERY defined.
>
> After I wrapped the
Compiling with SQLITE_OMIT_SUBQUERY, sqlite3ExprCodeIN() is compiled out
but at the same time still required at other places in expr.c.
As such, expr.c does not link well with SQLITE_OMIT_SUBQUERY defined.
After I wrapped the remaining references to sqlite3ExprCodeIN() by
#ifndef
6 matches
Mail list logo
