Re: Suggested ways to use an exceptions table

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Very nice.  Yeah, this is just a variation of a problem I have all the 
time: allowing an "all" value for a filter column.   Usually I use a 
specific placeholder value (like "*"), and so I can use IN like this:

WHERE FILTERFIELD IN (MYFIELD, '*')

MYFIELD is the data to be filtered, and FILTERFIELD is the selector.  
It's a little counter-intuitive because rather than testing MYFIELD, 
you're testing FILTERFIELD against either the filtered value or the 
placeholder, but it works nicely.


On 7/18/2019 10:13 AM, Rob Berendt wrote:
> Basically I am going to analyze some journals.  If we get notices about people and/or processes we care little about we can add them to the exceptions list.  Who and when they were added to the exceptions list are closely monitored by the table having these two columns:
>         Row_change_timestamp timestamp not null for each row on update as row change timestamp,
>          Change_user varchar(255) generated always as (current client_userid),
> Odd that it adds my user id in lower case.
>
> Rob Berendt