From: | David E(dot) Wheeler <david(at)kineticode(dot)com> |
---|---|
To: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: When is a record NULL? |
Date: | 2009-07-28 19:22:34 |
Message-ID: | F5020398-BEE9-467F-BD10-876F43EA87CE@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 27, 2009, at 5:19 PM, David E. Wheeler wrote:
> Yep, that's just what I needed, thanks. I think I'll send a patch
> for the "Cursors" section of the PL/pgSQL documentation that
> mentions this. Would have saved me a bunch of hassle.
So would have reading two more sentences of the docs, which state, to
my surprise (that I missed it!), “As with `SELECT INTO`, the special
variable <code>FOUND</code> can be checked to see whether a row was
obtained or not.” D’oh!
So now I've got things working the way I need, and I've blogged about
these SQL pathologies so that I don't forget.
http://www.justatheory.com/computers/databases/postgresql/neither-null-nor-not-null.html
Thanks for the help, everyone.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-07-28 19:25:02 | Re: system timezone regression failure |
Previous Message | pgsql | 2009-07-28 19:21:12 | xpath not a good replacement for xpath_string |