Re: Unable to add a new column to a table named "in" (look like a bug ...) - Mailing list pgsql-general

From Adam Rich
Subject Re: Unable to add a new column to a table named "in" (look like a bug ...)
Date
Msg-id 01de01c8a097$ed59cb90$c80d62b0$@r@sbcglobal.net
Whole thread Raw
In response to Re: Unable to add a new column to a table named "in" (look like a bug ...)  ("David Gagnon" <david.gagnon@cesart.com>)
Responses Re: Unable to add a new column to a table named "in" (look like a bug ...)  ("David Gagnon" <david.gagnon@cesart.com>)
Re: Unable to add a new column to a table named "in" (look like a bug ...)  ("David Gagnon" <david.gagnon@cesart.com>)
List 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.



pgsql-general by date:

Previous
From: Rodrigo Gonzalez
Date:
Subject: Re: Unable to add a new column to a table named "in" (look like a bug ...)
Next
From: "David Gagnon"
Date:
Subject: Re: Unable to add a new column to a table named "in" (look like a bug ...)