From: | Bob Vandy <srehtvandy(at)gmail(dot)com> |
---|---|
To: | pgadmin-support(at)postgresql(dot)org |
Subject: | Fwd: pgadmin3 -- adding CHECK constraint |
Date: | 2011-09-29 01:59:46 |
Message-ID: | CANVcEWM5u0m6xymWA4Hu8EJ6Dw1fHN8Y04nrbuponfGBEYDVWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Sorry about this post; I've figured out the problem. It's because I use
mixed-case in my table names and column names, so pgadmin3 quotes them. And
unless my other operations, (Constraints, queries, etc.), quote them as well
this problem occurs.
---------- Forwarded message ----------
From: Bob Vandy <srehtvandy(at)gmail(dot)com>
Date: Wed, Sep 28, 2011 at 7:04 PM
Subject: pgadmin3 -- adding CHECK constraint
To: pgadmin-support(at)postgresql(dot)org
I've googled and found no answer for the following:
(I'm using pgAdmin v 1.14.0)
I have a simple table with a column:
Status character varying(9) NOT NULL
I try to add a CHECK Constraint, whose definition is:
Status in ('Assigned', 'Deleted', 'Available')
When I click OK, I get an error:
ERROR: column "status" does not exist
What am I doing wrong?
If nothing, and this is a bug, how can I work around it?
Many thanks in advance for any help.
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2011-09-29 06:41:16 | Re: pgadmin3 -- adding CHECK constraint |
Previous Message | Bob Vandy | 2011-09-28 23:04:35 | pgadmin3 -- adding CHECK constraint |