Why does SQLite have to follow what PostgreSQL does? I thought SQLite is the leader.
Roman Sent from my T-Mobile 4G LTE Device -------- Original message -------- From: Richard Hipp <[email protected]> Date: 5/9/18 5:48 AM (GMT-05:00) To: SQLite mailing list <[email protected]> Subject: Re: [sqlite] 3.24 draft - upsert On 5/9/18, Olivier Mascia <[email protected]> wrote: > About: > > "Column names in the expressions of a DO UPDATE refer to the original > unchanged value of the column, before the attempted INSERT. To use the value > that would have been inserted had the constraint not failed, add the special > "excluded." table qualifier to the column name." > > Why using 'excluded' wording for this? Because that is what PostgreSQL does. I also thought that "new" would have been a better choice, but they didn't consult me. :-) -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
