From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Matteo Beccati" <m(dot)beccati(at)crpsoftware(dot)it>, <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Timestamp output |
Date: | 2002-02-27 03:17:05 |
Message-ID: | GNELIHDDFBOCMGBFGEFOOEJBCBAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc pgsql-sql |
> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > Although I know of this problem, I would also be interested in the fix.
> > I know that you can declare a column of type timestamp(0) to get the old
> > format, but how do you change an existing column?
>
> Officially, it's not supported. Unofficially, you can always hack
> pg_attribute.atttypmod, which is where precision info is stored.
> Observe the following example:
>
> regression=# create table foo (f1 timestamp, f2 timestamp(0));
> CREATE
> regression=# \d foo
> Table "foo"
> Column | Type | Modifiers
> --------+-----------------------------+-----------
> f1 | timestamp with time zone |
> f2 | timestamp(0) with time zone |
Hmmm...it seems to me that an easier way is to edit the pg_dump from the
previous version to add (0) in everywhere. Why don't we put that in the
'please be aware of these incompatibilites' section of HISTORY?
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-02-27 05:48:04 | Re: Timestamp output |
Previous Message | Benoit Menendez | 2002-02-26 19:26:27 | Re: Blob support... |
From | Date | Subject | |
---|---|---|---|
Next Message | Edward Murray | 2002-02-27 04:18:29 | Left Outer Join Question |
Previous Message | Stephan Szabo | 2002-02-26 22:30:43 | Re: About referential integrity. |