From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <AlbanColley(at)taskcare(dot)com>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: MS SQL Migration - Fix to migrate milliseconds |
Date: | 2003-09-08 18:42:58 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B844B5B2@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Alban,
Thanks, patch applied to CVS.
Regards, Dave.
> -----Original Message-----
> From: Alban Colley [mailto:AlbanColley(at)taskcare(dot)com]
> Sent: 08 September 2003 18:00
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] MS SQL Migration - Fix to migrate
> milliseconds
>
>
> Hi All
>
> I was attempting to migrate a large MSSQL2000 DB when I was
> surprised to be inform that I had duplicate entries on the
> primary key. I then update the type map for int to be int8
> and date to be timestamp which helped but still gave me
> problems. I then realised that the tables that where
> failings had timestamps as part of there primary keys (log
> tables). On investigation I found that the milliseconds
> where not being migrated.
>
> Issue:
>
> MSSQL2000 only show seconds by default for a select
> i.e. 2001-12-04 09:57:08.950 becomes 04-12-2001 09:57:09
>
> Fix:
>
> For timestamp fields replace 'select datefield from tables'
> with 'select CONVERT(char(30), datefield, 121) as datefield
> from table'
>
> This was harder than I expected as the current code does a
> select * to import the data which required me to create a field list.
>
> I have implemented this fix and attached is the patch and the
> Migrate_Data() procedure containing my mods.
>
> Alban
>
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2003-09-08 18:51:24 | frmMain_patch |
Previous Message | Alban Colley | 2003-09-08 17:00:09 | MS SQL Migration - Fix to migrate milliseconds |