From: Jodi Kanter <jkanter@virginia.edu>
To: Postgres SQL List <pgsql-sql@postgresql.org>
Subject: looking for empty fields
Date: Wed, 06 Aug 2003 10:07:29 -0400
Message-ID: <3F310BA1.2010701@virginia.edu> (raw)
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='';
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 <mailto:jkanter@virginia.edu>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jkanter@virginia.edu
Subject: Re: looking for empty fields
In-Reply-To: <3F310BA1.2010701@virginia.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox