Re: [HACKERS] empty dates and changing the default date behaviour

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Willy De la Court <Willy(dot)DelaCourt(at)pandora(dot)be>
Cc: "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] empty dates and changing the default date behaviour
Date: 2000-03-02 03:51:42
Message-ID: 7356.951969102@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Willy De la Court <Willy(dot)DelaCourt(at)pandora(dot)be> writes:
> you are right tom with the NULLs but I think I found an elegant
> solution to this

Interesting; I didn't realize that plpgsql supported functions returning
NULLs.

I wouldn't call it an "elegant" solution, by any means ;-). But if it
gets the job done for you, it'll do as a stopgap until datein() can
return a NULL itself.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-03-02 04:18:02 Re: [HACKERS] bitten by docs
Previous Message Willy De la Court 2000-03-02 00:49:55 RE: [HACKERS] empty dates and changing the default date behaviour