> It's not like it's hard to fix post-upgrade (or pre-upgrade, for that
> matter): a simple "ALTER TABLE ... SET DEFAULT now()" will do it.
Like 'now' and now() are both valid, at least will be good to have a note when a table
that includes 'now' is created, bringing the attention to people to
ROTECTED]>
To: "Nayib Kiuhan" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, October 15, 2003 10:50 AM
Subject: Re: [BUGS] timestamp bug 7.4beta3
> On Wed, 2003-10-15 at 02:08, Nayib Kiuhan wrote:
> > In versions before 7.4beta3 I use to have tables wi
Neil Conway <[EMAIL PROTECTED]> writes:
> I agree that this kind of silent backward-incompatibility isn't good,
It's unpleasant, but we were going to have to bite this bullet sooner or
later. Allowing 'now' to work like a non-constant in this context was
always a fragile hack.
> Tom, can we impr
On Wed, 2003-10-15 at 13:29, Nayib Kiuhan wrote:
> It is a good idea to through out an error during the table creation if
> the format is not as indicated (now()), because when I created my
> tables with the old format, it did not show any problem
I agree that this kind of silent backward-incompat
On Wed, 2003-10-15 at 02:08, Nayib Kiuhan wrote:
> In versions before 7.4beta3 I use to have tables with
> "date" timestamp DEFAULT 'now'
> It use to works properly, placing the actual date at the moment a new
> record was inserted. Now it always have the same date which correspond
> to the d
On Oct-15 2003, Wed, 02:08 -0400
Nayib Kiuhan <[EMAIL PROTECTED]> wrote:
> "date" timestamp DEFAULT 'now'
I believe you should be using
"date" timestampt DEFAULT CURRENT_TIMESTAMP(0)
--
Tomas Szepe <[EMAIL PROTECTED]>
---(end of broadcast)
POSTGRESQL BUG REPORT
TEMPLATE
Your
name
: Nayib KiuhanYour email address : [EMAIL PROTECTED]
