Tom Lane wrote:
Justin Wyer <[EMAIL PROTECTED]> writes:
I have this problem, I wrote a script to insert data into a table, one
of the columns is a birthdate now I only have the last two year digits,
and this all worked fine. Until I did a portupgrade (i am running on bsd
5.2.1 and 4.8 and postgresql 7.3.6 & 7.3.7 respectively) script worked
fine before the upgrade, now however, any year before 70 gets inserted
as 20xx and not 19xx.
My question is between which versions did this behaviour change, and is
there any way for me to force the old behaviour?
Don't you think it's time to fix your data? 2-digit years were a bad
idea from the get-go, but it was possible to get away with it for awhile
near the end of a century.
regards, tom lane
its not my data i am stuck moving this data from a sad access database
designed by a moron. anyway it means i will have to do alot of work on
the script to make it fix that, or just install an old version of pgsql
on a box here and pg_dump the table which seems easier.
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
