Some points on working table alias: 1. If upsert goes to trunk, there is already a INSERT table alias test case (do_execsql_test upsert3-210) that must succeed:
https://www.sqlite.org/src/info/907b5a37c539ea67 2. Obviously PostgreSQL already supports a working table alias universally: https://www.postgresql.org/docs/9.5/static/sql-insert.html INSERT INTO table_name [ AS alias ] [ ( column_name [, ...] ) ] https://www.postgresql.org/docs/9.5/static/sql-update.html UPDATE [ ONLY ] table_name [ * ] [ [ AS ] alias ] https://www.postgresql.org/docs/9.5/static/sql-delete.html DELETE FROM [ ONLY ] table_name [ * ] [ [ AS ] alias ] 3. In tables with serially related data it can be cumbersome to reference columns in the working table when columns must be computed from existing rows in the same table. The INSERT/UPDATE/DELETE working table alias would be very helpful and informative for readability in these situations. Peter On Tue, Apr 17, 2018 at 9:58 AM, Domingo Alvarez Duarte <mingo...@gmail.com> wrote: > Hello Richard ! > > Now that you are making changes on sqlite3 parser could you please add the > table alias to delete/insert/update ? > > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
