From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cannot drop column |
Date: | 2024-12-18 19:09:46 |
Message-ID: | CAKFQuwZSP+g5kp7apeAonRfT+ywMOGj712ONHDJAdjvo-kynVA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday, December 18, 2024, Rich Shepard <rshepard(at)appl-ecosys(dot)com>
wrote:
> On Wed, 18 Dec 2024, Rich Shepard wrote:
>
> Since your column name has an Upper case character, you will have to use
>>> double quotes to drop it. Try alter table statustypes drop column
>>> "Suspect";
>>>
>>
> Thanks for the lesson.
>>
>
> But,
>
> bustrac=# alter table statustypes drop column "Suspect"; ERROR: column
> "Suspect" of relation "statustypes" does not exist
> bustrac=#
>
> Double quoting didn't resolve the issue.
>
Red Ron’s email…
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-12-18 20:22:09 | Re: Using Expanded Objects other than Arrays from plpgsql |
Previous Message | Rich Shepard | 2024-12-18 19:09:05 | Re: Cannot drop column |