From: | Tom Lane <tgl> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src/backend/optimizer/prep (preptlist.c) |
Date: | 2000-07-22 06:19:05 |
Message-ID: | 200007220619.e6M6J5464327@hub.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Date: Saturday, July 22, 2000 @ 02:19:04
Author: tgl
Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/optimizer/prep
from hub.org:/home/projects/pgsql/tmp/cvs-serv64116
Modified Files:
preptlist.c
----------------------------- Log Message -----------------------------
Make update lists like 'UPDATE tab SET foo[1] = bar, foo[3] = baz'
work as expected. THe underlying implementation is essentially
'SET foo = array_set(foo, 1, bar)', so we have to turn the items
into nested invocations of array_set() to make it work correctly.
Side effect: we now complain about 'UPDATE tab SET foo = bar, foo = baz'
which is illegal per SQL92 but we didn't detect it before.
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2000-07-22 11:18:46 | pgsql/src/backend/access/common (indextuple.c) |
Previous Message | Bruce Momjian - CVS | 2000-07-22 04:45:10 | pgsql/doc/src/sgml/ref (pg_dump.sgml postgres-ref.sgml psql-ref.sgml reindex.sgml) |