diff options
author | Bruce Momjian <bruce@momjian.us> | 2004-08-10 17:30:47 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2004-08-10 17:30:47 +0000 |
commit | f7667e4cfaaed99d26bc4200fa98b2885e29080e (patch) | |
tree | 70b09f200b936da3e27678bd1f181376e4dbb73d /src/backend/utils/adt/regexp.c | |
parent | 2c29664b6bfefa8f7a4cc994c92fcb53a2a17962 (diff) | |
download | postgresql-f7667e4cfaaed99d26bc4200fa98b2885e29080e.tar.gz postgresql-f7667e4cfaaed99d26bc4200fa98b2885e29080e.zip |
Update DELETE FROM:
< * Allow DELETE to handle table aliases for self-joins
> * Allow an alias to be provided for the target table in UPDATE/DELETE
276,279c276,282
< There is no way to create a table alias for the deleted table for use
< in the DELETE WHERE clause. The agreed approach is to allow a USING
< clause to specify additional tables. UPDATE already has an optional
< FROM clause for this purpose.
> This is not SQL-spec but many DBMSs allow it.
>
> * Allow additional tables to be specified in DELETE for joins
>
> UPDATE already allows this (UPDATE...FROM) but we need similar
> functionality in DELETE. It's been agreed that the keyword should
> be USING, to avoid anything as confusing as DELETE FROM a FROM b.
Diffstat (limited to 'src/backend/utils/adt/regexp.c')
0 files changed, 0 insertions, 0 deletions