From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Carol Walter <walterc(at)indiana(dot)edu> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Can't drop constraint? |
Date: | 2009-05-05 16:08:51 |
Message-ID: | 18509.1241539731@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Carol Walter <walterc(at)indiana(dot)edu> writes:
> I don't know how they did this, but I have a table that has a compound
> field constraint. When I try to insert data into this table from an
> app I'd developing the query fails because the data supposedly
> violates the unique constraint on these fields. The fields are first,
> middle, and last names. The name I'm trying to insert doesn't exist
> in the database, yet I can't put it in. When I try to drop the
> constraint, which I can plainly see when I describe the table,
> postgres tells me that the constraint doesn't exist. How can I fix
> this?
Since you haven't shown us exactly what you're seeing, we're just
guessing ... but I'm wondering if the constraint has a mixed-case
name and you've forgotten to double-quote it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Cousin | 2009-05-05 16:27:47 | Re: can't cancel a query with pg_cancel_backend |
Previous Message | Carol Walter | 2009-05-05 15:23:42 | Can't drop constraint? |