RE : setNull() and =?

["Nicolas Grilly" <nicolas.grilly@xxxxxxxxxxxxxxxx>]

Jim wrote:
> Oracle is even more broken than that.  If you have a string 
> field and you set it to a blank string with
> 
>   update mytable set s = ''
> 
> then a select of the form
> 
>   select * from mytable where s = ''
> 
> will NOT find that row.  You must use
> 
>   select * from mytable where s is null

I think this behavior is correct. When you create your table, I guess
it's possible to define if void strings are authorized or not. If blank
strings are not authorized, they are transformed in null values. This is
why the first select statement doesn't work and the second one works.

Check your Oracle's documentation to see if it's possible to change
that. But perhaps I'm wrong...