Please try again with the latest pre-release snapshot. On 4/19/18, Quan Yong Zhai <q...@msn.com> 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 cnt=cnt+1 > > Before: > > wordcount --all :memory: sqlite3.c > > 2.406 wordcount --insert > > 2.296 wordcount --insert --without-rowid > > After: > > wordcount --all :memory: sqlite3.c > > 1.701 wordcount --insert > > 3.547 wordcount --insert --without-rowid > > > > As you can see, it’s very strangely ,in the table with rowid, the upsert > improved a lot, but in the table without rowidd, it’s slower than the origin > sql. > > > > > > Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows > 10 > > > > ________________________________ > From: sqlite-users <sqlite-users-boun...@mailinglists.sqlite.org> on behalf > of Richard Hipp <d...@sqlite.org> > Sent: Thursday, April 19, 2018 6:29:55 PM > To: General Discussion of SQLite Database > Subject: [sqlite] UPSERT available in pre-release > > The latest pre-release snapshot [1] contains support for UPSERT > following the PostgreSQL syntax. The documentation is still pending. > Nevertheless, early feedback is welcomed. You can respond either to > this mailing list, or directly to me. > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
-- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
