| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Matteo Beccati" <m(dot)beccati(at)crpsoftware(dot)it>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Timestamp output |
| Date: | 2002-02-27 05:48:04 |
| Message-ID: | 20074.1014788884@sss.pgh.pa.us |
| 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:
> Hmmm...it seems to me that an easier way is to edit the pg_dump from the
> previous version to add (0) in everywhere.
Well, sure, if you haven't loaded your dump yet.
Note, however, that this does *not* provide a closer approximation to
the behavior of older versions than 7.2 does by default. Older versions
do support fractional-second timestamps, though only to a couple of
digits IIRC.
The main thing that would be useful to avoid breaking client code that
can't handle fractional-second timestamps is to replace calls to
now() and current_timestamp with current_timestamp(0).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Lavergne | 2002-02-27 07:01:27 | Re: Blob support... |
| Previous Message | Christopher Kings-Lynne | 2002-02-27 03:17:05 | Re: Timestamp output |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | grep | 2002-02-27 05:53:06 | Bad design or SQL statment quandary |
| Previous Message | Christopher Kings-Lynne | 2002-02-27 05:23:56 | Re: Left Outer Join Question |