Just a quick note on the fix for the StandardNullBehavior=False problem with indexed columns coming up in 2.30 Build 2.  Per the release notes:

------------------------

The fix for incident report #4714:

# 4714 Queries on Indexed Integer Columns Not Working Properly with StandardNullBehavior Set to False

included some fairly significant changes to how indexed columns are compared with respect to NULLs, and this can cause changes in the results of queries, especially queries containing left outer joins that can produce NULLs. If you have turned off standard NULL behavior in the ElevateDB engine for your software, please be sure to review any existing queries to make sure that they are still working in the manner that you expect.

------------------------

We had one of the existing StandardNullBehavior=False tests fail because of the fix, and it was a query including LOJs that produced NULLs that child joins matched on because the child joins were on a table column that included NULLs in the underlying table.

Tim Young
Elevate Software
www.elevatesoft.com