On Mon, 11 Mar 2002, Bhuvan A wrote:
> If you compare a NULL with anything you don't
> get a true value whether you're comparing with
> =, !=, <, >, etc... That's how it's defined to
> where did you get this definition of behaviour!?
> is it applicable only to
> postgres or ..? its quite strange yaar!
I think that you are searching for a solution, so,
view the COALESCE SQL function in PostgreSQL
documentation. It will help you in your compares.
Juliano S. Ignacio
Do You Yahoo!?
Try FREE Yahoo! Mail - the world's greatest free email!
In response to
- Re: at 2002-03-11 17:02:09 from Stephan Szabo
pgsql-bugs by date
|Next:||From: pgsql-bugs||Date: 2002-03-11 21:59:08|
|Subject: Bug #613: Sequence values fall back to previously checkpointed value after crash|
|Previous:||From: Mozilla at Marela||Date: 2002-03-11 17:59:31|
|Subject: Critical: Pgsql inserts bad timestamp (seconds 60.00) - causes failing of backup-restore|