> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> HISTORY says, under "Migration to version 7.2":
TL> * The date/time value 'current' is no longer available. You
TL>will need to rewrite your applications.
I see now. Thanks. I didn't make the connection between "current"
and
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> Vivek Khera <[EMAIL PROTECTED]> writes:
>> "owner_lastbilled" date DEFAULT 'CURRENT_DATE' NOT NULL,
TL> The above was never correct. I believe that 7.1's rather lax date
TL> parser might have interpreted the literal as being 'current'. 7.2
Vivek Khera <[EMAIL PROTECTED]> writes:
> Then how come pg_dump outputs it that way? Is it because that's how I
> did it when creating the schema in the first place?
Presumably.
> TL> Because it is not one: it is a datatype behavioral change.
> It isn't documented in the HISTORY file in any wa
Vivek Khera <[EMAIL PROTECTED]> writes:
> "owner_lastbilled" date DEFAULT 'CURRENT_DATE' NOT NULL,
The above was never correct. I believe that 7.1's rather lax date
parser might have interpreted the literal as being 'current'. 7.2's
date parser would reject it, even if 'current' were still an
