addFoundSetFilterParam(), null, empty, & blank

Classic Servoy
1

I really like using addFoundSetFilterParam() to filter related foundsets, but run into problems when filtering for a column that contains a non-blank value. I do this:

		lofsfees.addFoundSetFilterParam('feeauthno','!=', null);
		lofsfees.addFoundSetFilterParam('feeauthno','!=', '');
		lofsfees.addFoundSetFilterParam('feeauthno','NOT LIKE', ' %');

But it seem like a lot of work, especially if filtering on more than one column. Is there an easier way than testing individually for nulls, empty strings, AND blank values (and even this only check that the first character is blank, not the entire column)?

2

msedita:
Is there an easier way than testing individually for nulls, empty strings, AND blank values

Well, I’d say no because NULL, empty and blank are 3 distinct values in SQL database world. If you need to check different omogeneous values you can consider using the IN operator (ex.: IN (1,2,5,7) or IN (‘a’,‘b’,‘c’) ) but NULL and empty needs to be treated differently in your DB. Maybe you could speed things up by setting that column to not accept the NULL value and then testing for LIKE ‘%’ (just from the top of my head, please double check).