| From: | Tom Lane <tgl(at)hub(dot)org> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql/src/backend/parser analyze.c |
| Date: | 2001-07-04 17:36:55 |
| Message-ID: | 200107041736.f64HatW61878@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
CVSROOT: /home/projects/pgsql/cvsroot
Module name: pgsql
Changes by: tgl(at)hub(dot)org 01/07/04 13:36:55
Modified files:
src/backend/parser: analyze.c
Log message:
Prohibit a column from appearing twice in a PRIMARY KEY or UNIQUE
constraint. This case (a) is useless, (b) violates SQL92, and
(c) is certain to cause a failure downstream when we try to create
an index with duplicated column names. So give an appropriate error
message instead of letting the index failure occur. Per report from
Colin Strickland. NOTE: currently, CREATE INDEX fooi ON foo(f1,f1)
still fails with 'cannot insert duplicate key' error. Should we
change that too? What about functional indexes?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut - PostgreSQL | 2001-07-04 21:22:56 | pgsql/ /configure onfig/java.m4 |
| Previous Message | Bruce Momjian - CVS | 2001-07-04 15:57:25 | pgsql/src/interfaces/jdbc/org/postgresql/core ... |