Re: Robust ways for checking allowed values in a column - Mailing list pgsql-general

From Rob Sargent
Subject Re: Robust ways for checking allowed values in a column
Date
Msg-id 7bcf6809-a959-5224-93db-645d15cd4359@gmail.com
Whole thread Raw
In response to Re: Robust ways for checking allowed values in a column  (Shaozhong SHI <shishaozhong@gmail.com>)
List pgsql-general
On 1/25/22 09:35, Shaozhong SHI wrote:
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.g.johnston@gmail.com> wrote:
On Tue, Jan 25, 2022 at 6:56 AM Shaozhong SHI <shishaozhong@gmail.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.


You would need to add form ~ 'expression' or form is null

And a body of held water is a reservoir (no 'a')

pgsql-general by date:

Previous
From: Shaozhong SHI
Date:
Subject: Re: Robust ways for checking allowed values in a column
Next
From: Shaozhong SHI
Date:
Subject: Counting the number of repeated phrases in a column