Re: A creepy story about dates. How to prevent it? - Mailing list pgsql-general

From scott.marlowe
Subject Re: A creepy story about dates. How to prevent it?
Date
Msg-id Pine.LNX.4.33.0306181102280.4992-100000@css120.ihs.com
Whole thread Raw
In response to Re: A creepy story about dates. How to prevent it?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: A creepy story about dates. How to prevent it?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: A creepy story about dates. How to prevent it?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
On Wed, 18 Jun 2003, Tom Lane wrote:

> =?iso-8859-1?Q?Conxita_Mar=EDn?= <comarin@telefonica.net> writes:
> > I suggest that maybe the pg_dump has to store the datestyle in order to
> > prevent this problems, no?
>
> In 7.3.3 and later, pg_dump forces ISO datestyle while dumping, to
> forestall exactly this problem.  Sorry that you got bit.
>
> When you're doing an update, it's often a good idea to use the newer
> version's pg_dump to extract the data from the older database.  We
> keep pg_dump compatible with back versions (presently it handles
> anything back to 7.0) so that you can take advantage of bugfixes in
> newer pg_dumps.  Like this one ...

That reminds me, did we get the date parsing fixed so that you can't
insert 22/03/2003 into a european database (or conversely, 03/22/2003 into
a US database) ?  I.e the problem where the date parser assumed you meant
it the other way...


pgsql-general by date:

Previous
From: Dennis Gearon
Date:
Subject: Re: Linux supports hot-swappable hardware? [was Re:
Next
From: "Ivar"
Date:
Subject: Re: Is it bug ?