Re: timestamp parse error --- *** Migration PLU

> -----Original Message-----
> From: Samuele Brignoli [mailto:samuele(dot)brignoli(at)darpha(dot)com]
> Sent: 28 March 2002 11:30
> To: Dave Page
> Subject: R: [pgadmin-support] timestamp parse error --- ***
> Migration PLU
>
>
> Ok Dave, here you are.
>
> Test creation create a table "Test" with only a datetime
> field. TestData is the data export ( but you can also insert
> a simple date like 10/10/2002 ). If you try to migrate this
> table with the plugin the usual error is generated (
> migrating the data, not generating the table ). Hope this help.

That migrates perfectly here from SQL Server 2000 to PostgreSQL 7.2/Cygwin.
The following extract from my logfile shows the migration:

2002-04-03 09:07:46 - Executing Plugin: Database Migration Wizard v1.3.21
2002-04-03 09:07:54 - Opening and Examining Source Database...
2002-04-03 09:07:54 - Opening connection: CATBERT Database: dave
2002-04-03 09:07:56 - Opened connection: Provider=SQLOLEDB.1;Integrated
Security=SSPI;Extended Properties="server=CATBERT;database=dave";Use
Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=PC9;Use Encryption for Data=False;Tag with column collation when
possible=False
2002-04-03 09:07:56 - Provider: SQLOLEDB.1 v2.7
2002-04-03 09:07:56 - Quote Character: '"'
2002-04-03 09:07:56 - Done - 2.15 Secs.
2002-04-03 09:07:56 - Looking for possible target databases...
2002-04-03 09:07:56 - Done - 0 Secs.
2002-04-03 09:08:01 - Searching for Foreign Keys...
2002-04-03 09:08:01 - Done - 0 Secs.
2002-04-03 09:08:03 - Migrating database...
2002-04-03 09:08:03 - Migration from Provider=SQLOLEDB.1;Integrated
Security=SSPI;Extended Properties="server=CATBERT;database=dave";Use
Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=PC9;Use Encryption for Data=False;Tag with column collation when
possible=False to helpdesk starting.
2002-04-03 09:08:03 - NOT NULL rules being honoured.
2002-04-03 09:08:03 - SQL (helpdesk): BEGIN
2002-04-03 09:08:03 - Creating table: Test
2002-04-03 09:08:03 - SQL (helpdesk): CREATE TABLE "Test" ( "date" timestamp
)
2002-04-03 09:08:03 - Migrating Data from: Test
2002-04-03 09:08:03 - Executing: SELECT * FROM "Test"
2002-04-03 09:08:03 - SQL (helpdesk): INSERT INTO "Test" ("date") VALUES
('1900-01-01 00:00:00')
2002-04-03 09:08:03 - SQL (helpdesk): INSERT INTO "Test" ("date") VALUES
('1900-01-01 00:00:00')
2002-04-03 09:08:03 - SQL (helpdesk): INSERT INTO "Test" ("date") VALUES
('1900-01-01 00:00:00')
2002-04-03 09:08:03 - SQL (helpdesk): INSERT INTO "Test" ("date") VALUES
('2002-12-25 00:00:00')
2002-04-03 09:08:03 - SQL (helpdesk): INSERT INTO "Test" ("date") VALUES
('2002-12-24 00:00:00')
2002-04-03 09:08:03 - SQL (helpdesk): INSERT INTO "Test" ("date") VALUES
('2001-12-24 00:00:00')
2002-04-03 09:08:03 - Records Copied: 6
2002-04-03 09:08:03 - SQL (helpdesk): COMMIT
2002-04-03 09:08:03 - Migration Completed!
2002-04-03 09:08:03 - Done - 0.48 Secs.

All I can suggest is that you double check your date format under 'Regional
Settings' on both your client and server.

Regards, Dave.