| From: | Shaozhong SHI <shishaozhong(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Robust ways for checking allowed values in a column |
| Date: | 2022-01-25 16:35:33 |
| Message-ID: | CA+i5JwbTugb+J4GO1V_adBEhOK8vbBWdu0f0XTzvytGR72=BQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
How about adding null as an alteration.
Would this be robust?
Regards,
David
On Tue, 25 Jan 2022 at 14:25, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Tue, Jan 25, 2022 at 6:56 AM Shaozhong SHI <shishaozhong(at)gmail(dot)com>
> wrote:
>
>> select form from mytable where form ~
>> '^Canal$|^Drain$|^Foreshore$|^inlandRiver$|^Lake$|^lockOrFlightOfLocks$|^Marsh$|^Researvoir$|^Sea$|^tidalRiver$|^Transfer$'
>>
>
> You do not need to repeat the boundary metacharacters on each branch. You
> can assert their presence just once and then use parentheses to group the
> alternations.
>
> form ~ '^(?Canal|Drain|etc...)$'
>
> David J.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Sargent | 2022-01-25 16:40:53 | Re: Robust ways for checking allowed values in a column |
| Previous Message | Tom Dearman | 2022-01-25 16:09:39 | Re: tstzrange on large table gives poor estimate of expected rows |