[sqlite] explain plan change between SQLite 3.8.3.1 and 3.8.11.1

On Thu, Aug 27, 2015 at 4:21 PM, Dominique Devienne wrote: > On Thu, Aug 27, 2015 at 3:37 PM, Richard Hipp wrote: > >> On 8/27/15, Clemens Ladisch wrote: >> > Dominique Devienne wrote: >> >> how can we programatically reliably discover which (v)tables a view >> >> accesses, staying in

[sqlite] explain plan change between SQLite 3.8.3.1 and 3.8.11.1

Dominique Devienne wrote: > One annoyance with the authorizer approach is that you cannot "stack them" Write your own authorizer that implements its own callback list. But the only sure way to prevent anyone else from installing its own authorizer is to change the function name in the SQLite

[sqlite] explain plan change between SQLite 3.8.3.1 and 3.8.11.1

At 11:58 31/08/2015, you wrote: >--- >But the only sure way to prevent anyone else from installing its own >authorizer is to change the function name in the SQLite library. >--- That wouldn't really work under Windows: GetProcAddress can provide access to a DLL function by index (ordinal

[sqlite] Documentation Error: sqlite3_set_authorizer() interface

According to the documentations of The Authorizer Action Codes (http://www.sqlite.org/c3ref/c_alter_table.html): Authorizer Action Codes /*** 3rd 4th ***/ #define SQLITE_SELECT 21 /* NULLNULL

[sqlite] Documentation Error: sqlite3_set_authorizer() interface

Hello ! Also there is no way to link the callback to specific statement, I think that an extra parameter with the whole sql statement would be needed and/or any other way to link several calls to a statement. Maybe something like: int sqlite3_set_authorizer(sqlite3*,int

[sqlite] I don't understand why I get "cannot start a transaction within a transaction"

On Mon, Aug 31, 2015 at 4:50 AM, Nicolas J?ger wrote: > I'm starting to use transaction in my C++ code to delete some entries > (tags) in my db. during execution, the first transaction (each > transaction is contained in one string), like : > > BEGIN TRANSACTION; > DELETE FROM TAGS WHERE NAME =

[sqlite] I don't understand why I get "cannot start a transaction within a transaction"

On 31 Aug 2015, at 2:23pm, Stephan Beal wrote: > Nope - you have only run the BEGIN part of the transaction. prepare() > prepares only one single statement, not multiples (you have 4 statements in > your SQL). Thus when you try to run another transaction, that BEGIN is > still open. In

[sqlite] combine SELECTs

On Sun, 30 Aug 2015 21:26:43 +0200 "R.Smith" wrote: > 1 - Sub-Queries: > > SELECT A.Data, B.Data, C.Data >FROM (SELECT KeyField, Col1 AS Data FROM someTable WHERE Col1 > > 5) AS A JOIN (SELECT KeyField, Col2 AS Data FROM someTable WHERE >