Re: [sqlite] 'replace ... do update...' crash

Thanks for the bug report. Now fixed on trunk and in the latest pre-release snapshot. https://www.sqlite.org/src/info/359725ab36339b44 On 4/20/18, Abroży Nieprzełoży wrote: > sqlite> .version > SQLite 3.24.0 2018-04-20 18:01:31 >

[sqlite] 'replace ... do update...' crash

sqlite> .version SQLite 3.24.0 2018-04-20 18:01:31 279c48f6061f766f5437edd6964c0dd1e10399314eb17b6e5ee34df925a7alt1 zlib version 1.2.11 msvc-1912 CREATE TABLE abc( a TEXT UNIQUE, b TEXT UNIQUE ); CREATE TABLE tt( id INTEGER PRIMARY KEY AUTOINCREMENT, x TEXT ); CREATE TRIGGER

Re: [sqlite] "Tagging" SQLite tables with attributes for introspection.

You could make a extra table that has a foreign key on sqlite_master and add extra attributes... You could add comments ( -- ) in the create statemtents; and parse those back out ... On Fri, Apr 20, 2018 at 3:52 PM, Randall Smith wrote: > I'm writing some code to do

[sqlite] "Tagging" SQLite tables with attributes for introspection.

I'm writing some code to do processing of some (but not quite all) of the tables in my SQLite database. I could make this a lot easier and more general purpose if I could somehow attach an attribute to the various tables that indicated whether that table should be processed. Other than, say,

[sqlite] Patch for Lemon that adds a command line option to allow specifying the output directory

Hi everybody, (Please keep CC'd in replies, as I am not subscribed to the mailing list.) As part of a personal project I made a small patch for Lemon which adds support for a "-d" command line option, which allows specifying the directory where the output files are to be placed. You can grab the

Re: [sqlite] UPSERT available in pre-release

I full agree with Petite Abeille. This upsert is quite limited, we can only insert one row on conflict update one row. Even so it is a big improvement versus the insert or replace, this is far from the merge from the SQL standard where we can insert or update multiple rows in one query. I am

Re: [sqlite] UPSERT available in pre-release

Please try again with the latest pre-release snapshot. On 4/19/18, Quan Yong Zhai wrote: > Dear Richard, > > I modified the wordcount.c in SQLite/test directory, to use the new upsert > command: > >INSERT INTO wordcount(word,cnt) VALUES(?1,1) ON CONFLICT(word) DO UPDATE > SET