I found a case where an "on conflict" clause generates an unexpected error, could this be an SQL parsing bug or grammar ambiguity?
trivee@work:~/test$ sqlite3 --version 3.29.0 2019-07-10 17:32:03 fc82b73eaac8b36950e527f12c4b5dc1e147e6f4ad2217ae43ad82882a88alt1 trivee@work:~/test$ sqlite3 test.db SQLite version 3.29.0 2019-07-10 17:32:03 Enter ".help" for usage hints. sqlite> create table src(id integer primary key); sqlite> create table dst(id integer primary key); sqlite> insert into dst(id) select id from src on conflict do nothing; Error: near "do": syntax error sqlite> insert into dst(id) select id from src where 1 on conflict do nothing; sqlite> -=- Vlad _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
