Re: pgMigrate

> -----Original Message-----
> From: Brett Maton [mailto:matonb(at)hotmail(dot)com]
> Sent: 11 January 2002 15:15
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] pgMigrate
>
>
> Hi,
>
> I have a problem with the Migration wizard, basically it
> chokes on a date
> field for some reason, it reckons that the exported date is
> something like
> 06/06/101. Not sure where it's getting this from as it's
> certainly not in
> the DB.
>
> I tried to alter pgMigrate to display the query string that
> was causing the
> problem (VB is not my thing so I probably just being stupid),
>

This should'nt be necessary (though your code looks OK. Under Tools ->
Options in pgAdmin, just set the Log Level to 'Debug' and then reconnect to
the target database. All the SQL & error messages should then end up in the
logfile (usually C:\pgAdmin_nnnn.log).

>
> but I get an error message when I try to run my modified plugin:
>
> An error has occured in pgAdmin II:frmMain.mnuPluginsPlg_Click:
>
> Number: 13
> Description: Type mismatch

That's a common one. Just make sure you have a complete matched set of dlls
- in particular pgAbsPlg.dll and pgSchema.dll. You should also make sure
your build is compatible with a stock pgMigration.dll.

> I'm not sure how the date / time is being passed to Postgres, but was
> thinking if it's sent over in a long string format (11
> January 2002) pg will
> store it correctly

Actually we normally use yyyy-MM-dd hh:mm:ss (ISO-8601?) which should work
no matter what your locale is. However, this doesn't appear to be the case
in this code - I'll look into it (probably be later today now).

Regards, Dave.