Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Ben Woosley <ben(dot)woosley(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints
Date: 2010-01-04 10:36:27
Message-ID: 1262601387.31658.0.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On mån, 2010-01-04 at 03:48 +0000, Ben Woosley wrote:
> However, unique and foreign key constraints added using the "alter
> table add
> constraint" syntax fail on the column name. At this point the
> statement has
> enough information (the host table name) to properly identify the
> column
> despite the unorthodox name. Alternatively, you could allow the .
> syntax
> qualification inside the argument to the constraint.

Example please?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2010-01-04 11:26:35 Re: BUG #5259: the table name double
Previous Message Toni Helenius 2010-01-04 10:29:22 BUG #5260: Postgre crashed unexpectedly