Hi,
It is not problem of mssql, it was defined in SQL 92 standard. There is
special command in tsql "SET ANSI_NULLS" which controls this behavior. This
command can be used as another workaround, if your jdbc driver supports some
sort of connection initialization. At least it's faster then wait for some
actions from orion guys. But in general, personally I am trying to avoid
using null values and use 0 instead, if it is possible.
Simon Salykov.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Christoph Sturm
> Sent: Wednesday, August 08, 2001 9:03 PM
> To: Orion-Interest
> Subject: handling null values in finders
>
>
> Hey all!
>
> I am using mssql with orion, and my problem is that my finders dont
> find null values.
> The problem is that orion just generates a whereclause "where x =
> null", and in tsql "no instance of null equals another instance of
> null", so the correct where clause would be "where x is null". I now
> write my queries all as "where $1 = $field or ($1 is null and $field
> is null) as a workaround, but I wonder if orion has some kind of
> special null handling.
>
> regarz
> chris
>
