| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Returning NULL from functions |
| Date: | 2001-09-20 02:01:51 |
| Message-ID: | 3BA94E0F.825B718F@fourpalms.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I am working on date/time stuff, and in the spirit of cleaning up
interesting but marginally useful features I've dropped support for
"invalid" for the timestamp and timestamptz types.
To help with upgrading, I thought that I'd map it to a NULL value, and
see the following in the regression tests:
-- Obsolete special values
INSERT INTO TIMESTAMP_TBL VALUES ('invalid');
ERROR: OidFunctionCall3: function 1150 returned NULL
Is this error message a feature of all returns of NULL, particular to
input routines, or can I somehow mark routines as being allowed to
return NULL values?
Comments?
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-09-20 02:12:34 | type casting troubles |
| Previous Message | Marc G. Fournier | 2001-09-20 01:08:59 | Re: CVS vs anoncvs (was Re: Case sensitive file names) |