Viorel
Thank you for responding and sorry to waste your time. I just realized my stupid mistake after sending the message! It was an integer field.
Jodi
Viorel Dragomir wrote:
----- Original Message -----
Sent: Wednesday, August 06, 2003 5:07 PM
Subject: [SQL] looking for empty fields
We recently upgraded from version 7.2.3 to 7.3.3 and seem to have some code that has broken. We were doing checks in various locations looking for nulls and/or empty fields. To search for empty fields we said something like
select count(am_pk) from arraymeasurement where al_fk is null or al_fk='';
It's a string value that you're searching for?
If not, don't use ''.
Is this not allowed anymore? All my check with the double ticks are failing. I assume there is a difference in postgres between an empty and null field. How can I check for both in 7.3.3?
Thanks
Jodi
--
_______________________________
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
jkanter@virginia.edu
<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->
<!--[if !supportEmptyParas]--> <!--[endif]-->
<!--[if !supportEmptyParas]--> <!--[endif]-->
<!--[if !supportEmptyParas]--> <!--[endif]-->
--
_______________________________
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
jkanter@virginia.edu
