Re: Odd behavior with NULL value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bsmith(at)h-e(dot)com (Bob Smith, Hammett & Edison, Inc(dot))
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Odd behavior with NULL value
Date: 2001-12-21 02:55:18
Message-ID: 12846.1008903318@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

bsmith(at)h-e(dot)com (Bob Smith, Hammett & Edison, Inc.) writes:
> On a related note, does anyone know if 'current' works with DATE?

DATE does not have an internal representation of 'current', so the DATE
input parser treats it the same as 'now'. AFAIR only timestamp (nee
datetime) has that concept.

FYI, the concept of 'current' has been deemed broken and removed
altogether for 7.2. See discussions in the pgsql-hackers archives
if you want to know why.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Stephan Szabo 2001-12-21 03:14:32 Re: Odd behavior with NULL value
Previous Message Phill Kenoyer 2001-12-21 01:22:35 Re: Odd behavior with NULL value