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: Accommodating alternative column values |
Date: | 2024-07-03 14:05:36 |
Message-ID: | CAKFQuwYGP6geSx61RUuvH07D+CDHWOiZNXi+WpB3U=QJ7h_Dgg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday, July 3, 2024, Rich Shepard <rshepard(at)appl-ecosys(dot)com> wrote:
> On Wed, 3 Jul 2024, Rich Shepard wrote:
>
> What I've tried:
>> bustrac=# alter table people alter column email set data type varchar(64)
>> [];
>> ERROR: column "email" cannot be cast automatically to type character
>> varying[]
>> HINT: You might need to specify "USING email::character varying(64)[]".
>>
>
> What I forgot to mention is that the current datatype is varchar(64) and I
> want to make it an array.
>
>
Yeah, the simply cast suggested will not work. You’d have to apply an
expression that turns the current contents into an array. The current
contents are not likely to be an array literal.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Torsten Förtsch | 2024-07-03 14:06:45 | Re: Accommodating alternative column values |
Previous Message | Torsten Förtsch | 2024-07-03 14:04:21 | Re: Accommodating alternative column values |