Ultimately, I'm fine diverging from the standard way of doing things
to make null equality work as expected from an object programmer's
perspective. However, in cases where the programmer is sure there
cannot be nulls, it would be great to have some technique to specify
that A = B should be used instead of (A is null and B is null) or (A
is not null and B is not null and A = B) [ See
http://216.121.112.228/browse/NH-2398 ]. If the decision is to go the
"object emulation route," as is in the code so far, I'd at least like
to allow the expression to be a dialect-specific thing, since some
databases can use IS DISTINCT FROM or <=>.
Things seem a little slow around the list this week. Maybe everyone's
in crazy work mode like we've been recently. :)
Patrick Earl
