Ok, thanks. that's what i get for using a premade package, I guess.
On Feb 15, 2004, at 1:31 PM, Tom Lane wrote:
> Harry Hochheiser <hsh(at)nih(dot)gov> writes:
>> Running Postgres 7.4 on Panther, there seems to be a problem with
>> setting a timestamp column to have a default of 'now':
> There was an intentional change of behavior --- see the release notes.
> The supported way to do this is to use CURRENT_TIMESTAMP or now() as
> the column default.
> regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Pavel Stehule||Date: 2004-02-17 10:48:35|
|Subject: plpgsql - variable's names conflict with table field names|
|Previous:||From: Chris Campbell||Date: 2004-02-15 21:50:41|
|Subject: Crash when calling a pl/pgsql function with no row to pass as an argument|