× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.