Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-11 Thread David Raymond
compatibility of indexes with "WHERE function()" ... Language rules are never quite strict rules... it's just a description and rule-based understanding of how people speak, and if that changes over time, so must the rules that describe it. I cringe to think it, but probably some day these sent

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-09 Thread Jens Alfke
> On Oct 8, 2016, at 1:39 PM, Richard Hipp wrote: > > See http://sqlite.org/graphs/size-20161009.jpg > for a graph of > compiled-binary size using gcc 4.8.4 and -Os on x64 Linux. Less than > 0.5 MB, though to be fair this is

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-09 Thread Simon Slavin
On 9 Oct 2016, at 9:32am, R Smith wrote: > most everybody else in the World (including North America) seems to more > easily understand "Indexes" as the plural That's why I used it here. Formal English requires that I write 'indices' and that's what I used when I started

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-09 Thread R Smith
On 2016/10/08 9:41 PM, Jens Alfke wrote: —Jens * is it ‘indexes’ or ‘indices’, in computer science? It is both, and I pedantically prefer "Indices", but there's been some debate and you can find on-line literature in support of all views. The correct original "English" is of course

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-08 Thread Richard Hipp
On 10/8/16, Jens Alfke wrote: > > SQLite is only about 1MB of > code(?) See http://sqlite.org/graphs/size-20161009.jpg for a graph of compiled-binary size using gcc 4.8.4 and -Os on x64 Linux. Less than 0.5 MB, though to be fair this is without extensions such as FTS5 or

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-08 Thread Jens Alfke
> On Oct 8, 2016, at 12:56 PM, Richard Hipp wrote: > > Databases that use functions in the WHERE clause of a partial index > will be unreadable by any version of SQLite prior to 3.15.0. Yikes! This would be good to call out in the docs. > Why can't you statically link against

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-08 Thread Richard Hipp
On 10/8/16, Jens Alfke wrote: > What’s the compatibility of the new partial indexes* with deterministic > functions in their WHERE clauses? > I.e. if I create such an index, and then later the database is opened by an > older version of SQLite, what happens? (Let’s say the

[sqlite] Backward compatibility of indexes with "WHERE function()"

2016-10-08 Thread Jens Alfke
What’s the compatibility of the new partial indexes* with deterministic functions in their WHERE clauses? I.e. if I create such an index, and then later the database is opened by an older version of SQLite, what happens? (Let’s say the function used in the WHERE clause is still properly