A merry Christmas to you (and your beloved ones), and all pgAdmin developers.
Dave Page wrote:
I filed a bug report with RedHat : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=80394Hi Didier, Glad it's working now. It might be worth mentioning in your report, that the error appears to be coming from MDAC rather than pgAdmin. It appears the MDAC (or a component of it that pgAdmin uses) is being destroyed for some reason. The error message you are getting is basically the same as you get from an app when you are debugging a COM object in VB that the app is using, and you stop the debug.
It would be much appreciated, if you can add your comments (as I'm not a VB developer).
On a related note :
1. Access2K database migration with 1.4.12 is approx. 6 to 8 times slower than previous versions (20 minutes -> over two hours), mainly in the Foreign Key creation, it seems. I'll check if this is due to pgAdmin (1.4.0 -> 1.4.12) or PostgreSQL (7.2.x -> 7.3).
2. Total migration execution time doesn't wrap around :
...
Creating Foreign Key: invoicesstock
Creating Foreign Key: ordersstock
Creating Foreign Key: balancessubjobs3
Creating Foreign Key: budgetssubjobs3
Migration finished at: 24/12/2002 0:20:16, taking -77438,65 seconds.
3. The 'default values' of my Access2K fields do not get migrated : is this a bug or a missing feature ?
Kind regards,
Didier
--
Didier Moens
-----
RUG/VIB - Dept. Molecular Biomedical Research - Core IT
tel ++32(9)2645309 fax ++32(9)2645348
http://www.dmb.rug.ac.be
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
