Re: [sqlite] SQLite 3.20.0 postponed

> Le 22 juil. 2017 à 08:14, Gwendal Roué a écrit : > > Still, I feel that static strings are a weird way to define keys. For > example, value subtypes in SQLite have the same requirement of needing > "unique subtype identifiers", and those subtypes are, today, ints.

Re: [sqlite] Database version

I have a routine that reads the first chunk of any file to see if it contains the SQLite header. That way I can be sure that what I'm opening is at least a SQLite database, I can skip on a Malformed Database error when trying to open a renamed BMP, and I have the security knowing that if files

Re: [sqlite] Trigger firing order

On 21/07/2017 18:13, petern wrote: a programming pattern that is missing in SQLite trigger body: "if (new.C1 <> old.C1) then ". It can be simulated for updates ("update ... where ... and new.C1 <> old.C1") but not for inserts ("insert" has no "where" clause). Maybe so. But, INSERT can accept

Re: [sqlite] SQLite 3.20.0 postponed

> Le 21 juil. 2017 à 18:50, Richard Hipp a écrit : > > On 7/21/17, Gwendal Roué wrote: >> >> First, this strcmp() give a lot of work to languages that wrap SQLite and >> lack support for "static strings". > > But sqlite3_result_pointer() and

Re: [sqlite] UPDATE database using parameters

On Friday, 21 July, 2017 20:05, Jens Alfke said: >> On Jul 21, 2017, at 1:01 PM, Keith Medcalf >> wrote: >> Just using a web browser has your machine executing god only knows >> what code generated by god only knows who doing god only knows what >> to

Re: [sqlite] Trigger firing order

On 21/07/2017 19:00, Simon Slavin wrote: I’m minded to leave things as they are, with the order undefined. If you really want to trigger a number of different operations in a specific order, put those operations all in one trigger, one after another. Yes, possible now with the reminder of

[sqlite] Evaluation of SQLite SEE

Hello, I see that a license is required to download SQLite SEE. Is it possible to get a temporary license to evaluate? We would like to test the performance impact of encryption on our application. Thank you, Adrian ___ sqlite-users mailing list

[sqlite] Surprising result from changes() after constraint violation

Running Sqlite 3.19.3, an insert failed because of a constraint violation and the return value from changes() was not what I would have expected. Why did "select changes()" return "3" on the second call, even though nothing was inserted into the db? sqlite> pragma foreign_keys=1; sqlite>

Re: [sqlite] Surprising result from changes() after constraint violation

On 21 Jul 2017, at 10:50pm, Steven Friedman wrote: > sqlite> insert into t2 (c1) values (1); > Error: foreign key mismatch - "t2" referencing "t1" > sqlite> select changes(); "changes()" is returning the value of the last /successfull/ command which makes