From: | NikhilS <nikkhils(at)gmail(dot)com> |
---|---|
To: | "Neil Conway" <neilc(at)samurai(dot)com> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Trevor Hardcastle" <chizu(at)spicious(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: CREATE TABLE LIKE INCLUDING INDEXES support |
Date: | 2007-05-17 13:09:15 |
Message-ID: | d3c4af540705170609n21911a2ja9314d4db9d230d3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Hi,
>
> Nope:
>
> neilc=# create table t1 (a int, b int);
> CREATE TABLE
> neilc=# create unique index t1_a_idx on t1 ((a + b)) where (a > 5);
> CREATE INDEX
I just now realized that even though we allow the above. We do not allow:
pg=# create table t1 (a int, b int, unique(a+b));
nor the where clause syntax.
Any specific reason for this behaviour?
If we want to pass such kinds of expr, predicate based constraints via the
"LIKE .. INCLUDING CONSTRAINTS" statements, transformIndexConstraints as
well as the Constraint structure might need modifications.
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-05-17 13:22:17 | Re: Lack of urgency in 8.3 reviewing |
Previous Message | Robert Treat | 2007-05-17 12:53:49 | Re: Not ready for 8.3 |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-05-17 13:10:43 | Re: Updateable cursors patch |
Previous Message | FAST PostgreSQL | 2007-05-17 08:43:54 | Re: Updateable cursors patch |