Skip site navigation (1) Skip section navigation (2)

Re: comparing rows

From: Don Baccus <dhogaza(at)pacifier(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Magnus Hagander <mha(at)sollentuna(dot)net>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: comparing rows
Date: 2000-08-03 14:35:13
Message-ID: 3.0.1.32.20000803073513.014e3690@mail.pacifier.com (view raw or flat)
Thread:
Lists: pgsql-hackers
At 10:22 AM 8/3/00 -0400, Bruce Momjian wrote:
>> Oracle allows it, and returns NULL.  Oracle's fairly trustworthy
>> on low-level standards compliance over things like NULL (not
>> entirely, though - it treats '' as NULL in the VALUES list of
>> an INSERT, though not elsewhere, for instance).
>
>So you can't get a zero-length string into a column in Oracle. 
>Interesting.

The killer is it makes porting from Oracle to Postgres or another
DB that does it right a pain in the ass.

I've got a lot of experience with this particular issue due to the
OpenACS web toolkit (arsDigita's stuff ported from Oracle to Postgres).



- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
  Nature photos, on-line guides, Pacific Northwest
  Rare Bird Alert Service and other goodies at
  http://donb.photo.net.

In response to

pgsql-hackers by date

Next:From: Don BaccusDate: 2000-08-03 14:37:17
Subject: Re: comparing rows
Previous:From: Don BaccusDate: 2000-08-03 14:32:36
Subject: Re: comparing rows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group