Have you looked at transform_null_equals in the postgresql.conf file to
see if turning that on makes this work like oracle?
On Wed, 2 Oct 2002, Mario Weilguni wrote:
> Ok, I checked this again. Up until 7.2, it was possible to compare an empty string
>to a number, and it worked::
> e.g.: selec
On Wed, 2 Oct 2002, Mario Weilguni wrote:
> >> But oracle accepts this one:
> >> SQL> select * from re_eintraege where id='';
> >> no rows selected
> >> because oracle treats the empty string as NULL
> >
> >Oracle does that for string data, but it doesn't do it for numerics
> >does it? In any ca
>> But oracle accepts this one:
>> SQL> select * from re_eintraege where id='';
>> no rows selected
>> because oracle treats the empty string as NULL
>
>Oracle does that for string data, but it doesn't do it for numerics
>does it? In any case, that behavior is surely non-compliant with
>the SQL s
Mario Weilguni <[EMAIL PROTECTED]> writes:
> Ok, I checked this again. Up until 7.2, it was possible to compare an empty string
>to a number, and it worked::
> e.g.: select * from mytable where int4id=''
> worked fine, but delivered no result.
No, that was not what it did: in reality, the '' wa
Ok, I checked this again. Up until 7.2, it was possible to compare an empty string to
a number, and it worked::
e.g.: select * from mytable where int4id=''
worked fine, but delivered no result. This is exactly what Oracle did here,
a comparison like this does not work:
SQL> select * from re_ein
