Fwd: pgadmin3 -- adding CHECK constraint
| От | Bob Vandy |
|---|---|
| Тема | Fwd: pgadmin3 -- adding CHECK constraint |
| Дата | |
| Msg-id | CANVcEWM5u0m6xymWA4Hu8EJ6Dw1fHN8Y04nrbuponfGBEYDVWA@mail.gmail.com обсуждение исходный текст |
| Ответ на | pgadmin3 -- adding CHECK constraint (Bob Vandy <srehtvandy@gmail.com>) |
| Ответы |
Re: Fwd: pgadmin3 -- adding CHECK constraint
|
| Список | 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@gmail.com>
Date: Wed, Sep 28, 2011 at 7:04 PM
Subject: pgadmin3 -- adding CHECK constraint
To: pgadmin-support@postgresql.org
From: Bob Vandy <srehtvandy@gmail.com>
Date: Wed, Sep 28, 2011 at 7:04 PM
Subject: pgadmin3 -- adding CHECK constraint
To: pgadmin-support@postgresql.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.
В списке pgadmin-support по дате отправления: