Thank you for your answer. I tried before with 'now()' (inside the single aspen) and didn't work . Now it is working very well without the aspens as you already mentioned. 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 just figure out that something was wrong with my tables once my java program start to do weird things.
Again, many thanks, Nayib ----- Original Message ----- From: "Neil Conway" <[EMAIL PROTECTED]> 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 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 date at creating the table. > > >From the 7.4 HISTORY file: > > 'now' will no longer work as a column default, use now() (change > required for prepared statements) (Tom) > > Admittedly, this change should also be noted in the 'migration to 7.4 > section' of the release notes -- I'll send a patch to this effect to > pgsql-patches. > > -Neil > > > ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
