Re: CREATE TABLE LIKE INCLUDING INDEXES support

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: NikhilS <nikkhils(at)gmail(dot)com>
Cc: "Neil Conway" <neilc(at)samurai(dot)com>, "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 14:31:59
Message-ID: 25508.1179412319@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

NikhilS <nikkhils(at)gmail(dot)com> writes:
> 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));

> Any specific reason for this behaviour?

It'd be contrary to SQL spec. The UNIQUE constraint takes a list of
column names, full stop.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Cui Shijun 2007-05-17 14:36:23 Re: Lack of urgency in 8.3 reviewing
Previous Message Andrew Dunstan 2007-05-17 14:20:50 Re: UTF8MatchText

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-05-17 15:27:49 Re: Patch for seq scan & scan resistant bufmgr
Previous Message Andrew Dunstan 2007-05-17 14:20:50 Re: UTF8MatchText