Re: Unable to add a new column to a table named "in" (look like a bug ...)

From: "Adam Rich" <adam(dot)r(at)sbcglobal(dot)net>
To: "'David Gagnon'" <david(dot)gagnon(at)cesart(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unable to add a new column to a table named "in" (look like a bug ...)
Date: 2008-04-17 14:32:55
Message-ID: 01de01c8a097$ed59cb90$c80d62b0$@r@sbcglobal.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> It worked Thanks!! But there is definitly something wrong with the
> error
> message I got (right?):
>
> reference=# alter table "IN" add column INDESCS VARCHAR[];
> ERROR: column "indescs" of relation "IN" already exists
>

I don't know, what do you see when you \d "IN" ?

When you use double-quotes, capitalization is significant,
So "in" and "IN" and "In" are all different tables. This error
message means you already have an upper-case "IN" table and it
already has a column INDESCS.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Enke 2008-04-17 15:09:36 good experience with performance in 8.2 for multi column indexes
Previous Message Rodrigo Gonzalez 2008-04-17 14:30:44 Re: Unable to add a new column to a table named "in" (look like a bug ...)