> On Apr 19, 2018, at 1:06 PM, Richard Hipp <d...@sqlite.org> wrote: > > We are open to adding MERGE INTO at some point in the future.
Excellent! > But the UPSERT syntax is both easier to understand Debatable. > and easier to implement, Possibly. > and we prefer to follow PostgreSQL syntax whenever possible. See > https://wiki.postgresql.org/wiki/UPSERT#SQL_MERGE_syntax for > PostgreSQL's rationale for rejecting MERGE. Let’s agree to disagree on that long running opinion piece. MERGE, as per SQL:2003 & SQL:2008 & co. is the way to go. The situation remind me of the introduction of recursive common table expression (CTE) in SQLite, which at first you wanted to implement solely in terms of Oracle’s 'CONNECT BY’ syntax, but ultimately saw the benefit of embracing the full-fledged CTE syntax instead. And I’m personally very grateful for that thought process which gifted SQLite a kickass CTE implementation. Thanks for that! Hopefully, the UPSERT vs. MERGE conversation will move that way as well: MERGE FTW! :) _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
