Problem with Hilite editor and dates

[senordhuff]

Hi,

Here is a problem we see that we recreated in your feature explorer here: http://www.smartclient.com/#userDefinedHilites

Edit Hilites and select:
nationhood > less than > enter 09/12/1947 in the from field > Background > #CCFFFF >Save

It only highlights the rows with no Nationhood date with the color and fails to highlight some of the rows that are less than 09/12/1947

[Isomorphic]

That issue is already fixed in SC 8.3d, but we are able to reproduce in it SC 8.2p.

[senordhuff]

Ok, so just double-checking then, does that mean you are able to reproduce it in 8.2 and you are now going to work on a fix for 8.2?

[Isomorphic]

We do see the issue in 82; we're analyzing the problem now.

Note, as a workaround, you can use the AdvancedHiliteEditor--the rule you describe works perfectly there.

[Isomorphic]

We have applied a fix to the SC 8.2p/SGWT 3.0p branch; the next nightly build should have it.

[senordhuff]

Looks like you applied some date handling enhancments to the hilite editor UI. They look nice. And, it looks like the problem is mostly fixed.

The only issue I see with dates is that the hilite logic will evaluate a null value as less than the date entered instead of ignoring it if you use the "less than" clause. Is there a way to easily edit the logic to not apply formatting to a null date in this case?

[Isomorphic]

As with criteria in general, we don't want it to the be that case that null is treated in the odd way it is in SQL - see DataSource.strictSQLFiltering for background.

[senordhuff]

Are you saying we can use the strictSQLFiltering property to alter thsi behavior? Or, this behavior is not changeable because of the issues discussed regarding strictSQLFiltering ?

[Isomorphic]

We're saying we think the behavior is the right one because ignoring null for both greaterThan and lessThan leads to the bizarre consequences listed under the strictSQLFiltering doc. We haven't put in any kind of customization hook that would allow this to be easily changed, it would involve something like custom operators and probably isn't worth it.