From: | "awais" <awais(at)techlogix(dot)com> |
---|---|
To: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | problem with new postgresql driver |
Date: | 2002-03-14 11:32:29 |
Message-ID: | 009201c1cb4b$ecc87370$1700a8c0@awais |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
We have a table named "atm" in our database which is uing latest driver of postgresql, it has a column named "location", all records (which are more than 1) of "atm" table have this column value set as (null). When we executed the query "select * from atm where location=null ", 0 rows were returned, which was not we were expecting.
We have another database using previous driver of postgresql, it also has a table named "atm" with a column named "location", similarly all records (which are more than 1) of "atm" table have this column value set as (null), when we executed the query "select * from atm where location=null ", all rows were returned, which was according to our expectations.
Can u please describe how to tackle this problem.
regards,
Awais
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Pfau | 2002-03-14 15:12:26 | Re: comparing null value in plpgsql. |
Previous Message | pgsql-bugs | 2002-03-14 11:15:19 | Bug #614: Incorrect parse with time function |