From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Converting yes or no to one letter strings. |
Date: | 2019-06-04 23:44:43 |
Message-ID: | alpine.LNX.2.20.1906041643490.12623@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 4 Jun 2019, David G. Johnston wrote:
> Actually, given that "f" is becoming multiple different values it seems
> like the OP is improving upon their data model. That should very much be
> done at the table level at not relegated to views, let alone a UI layer.
>
> It is not unusual to want to convert something that was a simple boolean
> to an enumeration of values. Though it is probably better to add a new
> column to reflect the new model element and effectively deprecate the old
> column - eventually removing it from use when it is no longer needed.
> Altering the column type, while possible, is not usually desirable. In
> particular it makes rolling back (or supporting older) client software
> more difficult because the old version will not recognize the new field
> and the old field will be gone.
David,
Thanks for the insights.
Rich
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-06-05 00:19:33 | Re: Converting yes or no to one letter strings. |
Previous Message | David G. Johnston | 2019-06-04 23:29:27 | Re: Converting yes or no to one letter strings. |