From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Laurette Cisneros" <laurette(at)nextbus(dot)com>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: timestamp column default changed? |
Date: | 2002-09-12 02:10:12 |
Message-ID: | GNELIHDDFBOCMGBFGEFOKEDDCEAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
timestamp becoming timestamp without time zone is actually the SQL
standard...
Chris
> I'm sure you all have discussed this ad-nauseum but this sure
> does create a
> pain in the butt when converting.
>
> Ok, I had my say.
>
> Thanks for all your hard work,
>
> L.
> On Wed, 11 Sep 2002, Bruce Momjian wrote:
>
> > Laurette Cisneros wrote:
> > >
> > > If you define a column as:
> > > col timestamp
> > > In 7.2.x didn't it default to timestamp with timezone?
> > >
> > > And now in 7.3(b1) it defaults to timestamp without timezone?
> >
> > /HISTORY says right at the top:
> >
> > * TIMESTAMP and TIME data types now default to WITHOUT TIMEZONE
> >
> >
>
> --
> Laurette Cisneros
> The Database Group
> (510) 420-3137
> NextBus Information Systems, Inc.
> www.nextbus.com
> ----------------------------------
> A wiki we will go...
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2002-09-12 02:11:46 | Re: - pg_dump issues |
Previous Message | Serguei Mokhov | 2002-09-12 02:07:23 | Re: fix for palloc() of user-supplied length |