From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'Brett Maton'" <matonb(at)hotmail(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: [pgadmin-hackers] pgMigrate |
Date: | 2002-01-14 10:16:19 |
Message-ID: | FED2B709E3270E4B903EB0175A49BCB1047416@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Brett Maton [mailto:matonb(at)hotmail(dot)com]
> Sent: 12 January 2002 14:49
> To: dpage(at)vale-housing(dot)co(dot)uk
> Subject: RE: [pgadmin-hackers] pgMigrate
>
>
> Hi Dave,
>
> Thanks for the letting me know about the logs, guess I
> should have looked
> around a little more ;). I did find the offending field not
> sure how they
> managed to get that value in thier in the first place!
>
> Looking through the log though it would appear that the
> Access Date/Time
> field is out put as dd/mm/yy in single quotes. Is this
> affected by the
> format value setup in the Access DB ?
Hi Bret,
I've committed a fix to CVS that should sort this. All dates are reformatted
to yyyy-MM-dd hh:mm:ss which is unambiguous. The VB Format function will
also prefix 1899-12-30 automatically for MS Access date fields that only
actually contain the time (I'm sure this must be broken behaviour on the
part of Access, but it happens a lot so we need to handle it somehow).
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Brett Maton | 2002-01-14 13:29:57 | Re: [pgadmin-hackers] pgMigrate |
Previous Message | Dave Page | 2002-01-14 08:31:07 | Re: [pgadmin-hackers] pgMigrate |