Re: case sensititvity bug in foreign keys on cygwin - Mailing list pgsql-general

From Mike Smialek
Subject Re: case sensititvity bug in foreign keys on cygwin
Date
Msg-id 9vlv02$2hor$1@news.tht.net
Whole thread Raw
In response to ecpg - select * into structure problem  ("Tim Nelson" <nelsonx@earthlink.com>)
List pgsql-general
Mike Smialek wrote:
>
> Configuration:
>     Windows 2000 Server
>     cygwin 2.78.2.9
>     PostgreSQL 7.1.3
>     psqlODBC 7.1.8
>     pgAdmin II 1.1.66
>
> Bug:
>     Capital letters cannot be used in column names used in foreign key
> constraints
>
>     All Smalls succeeds:

[snip]

>     Capitalizing just the foreign column name fails with what seems to be
an
> incorrect error:
>         -- Table: significance
>         CREATE TABLE "significance" (
>         "Significanceid" int4 NOT NULL,
>         "desc" varchar(255),
>         CONSTRAINT "pk_significance" PRIMARY KEY ("Significanceid"));
>
>         -- Table: primaryword
>         CREATE TABLE "primaryword" (
>         "exerciseid" int4 NOT NULL,
>         "significanceid" int4 NOT NULL,
>         CONSTRAINT "pk_primaryword" PRIMARY KEY ("exerciseid"),
>         CONSTRAINT "fk_primaryword_significance" FOREIGN KEY
> (significanceid) REFERENCES "significance" (Significanceid) );

You aren't double quoting the column name Significanceid
in the foreign key contraint clauses. Why ?

regards,
Hiroshi Inoue

That is DDL returned from pgAdminII.  The quotes appear to be optional if
you are using all lower case.  With the Quotes, the mixed case works.
Thanks,
MS





pgsql-general by date:

Previous
From: Olcsák József
Date:
Subject: ABSTIME = UNINX TIMESTAMP???
Next
From: Steven Lane
Date:
Subject: postgres 7.1on Mac OS 10.1