Обсуждение: Status of Migration Wizard ?
Hi all, Not wanting to put pressure on the developers ;) , but is there any progress on the MSAccess Migration Wizard ? PgAdmin II v1.1.66 is stated to be feature-complete, however, the MW is still on the todo-list, and is not to be found in the CVS. Should the MW be postponed to a future release cycle : - are there any (planned) improvements wrt the MW in PgAdmin 7.1 ? - any improvements wrt PostgreSQL 7.2 ? - is it possible to lift a prerelease out of the CVS ? Congrats with an otherwise very nice tool. Sincerely, Didier Moens ----- RUG/VIB - Dept. Molecular Biology - Core IT tel ++32(9)2645309 fax ++32(9)2645348 http://www.dmb.rug.ac.be
> -----Original Message----- > From: Didier Moens [mailto:Didier.Moens@dmb001.rug.ac.be] > Sent: 12 November 2001 11:16 > To: pgadmin-support@postgresql.org > Subject: [pgadmin-support] Status of Migration Wizard ? > > > Hi all, > > > Not wanting to put pressure on the developers ;) , but is there any > progress on the MSAccess Migration Wizard ? > > PgAdmin II v1.1.66 is stated to be feature-complete, however, > the MW is > still on the todo-list, and is not to be found in the CVS. > Should the MW be postponed to a future release cycle : > - are there any (planned) improvements wrt the MW in PgAdmin 7.1 ? > - any improvements wrt PostgreSQL 7.2 ? > - is it possible to lift a prerelease out of the CVS ? > > I don't recall saying that pgAdmin II *is* feature complete, but anyway the story is: 1) I wanted to redesign the Migration Wizard as it worked well for Access, but not other DBs. 2) The new design was based on the concept of building an object hierarchy from the source database that could be modified in any way required before building the target database. Data could then be filtered across though user definable VB or JavaScripts (using the MS scripting Engine). 3) In order to do this, I needed to get certain details (e.g. fkey, pkey) from the source database. To get this info, I was using direct OBDC API calls. Unfortunately, it turns out that whilst the ODBC spec allow me to get the required info, the MS Access & SQL Server ODBC drivers don't support that level of functionality (neither does psqlODBC btw), and basically I couldn't do what was required on the 2 most popular source database types :-( Currently I have the bginnings of a pgAdmin II Migration Wizard Plugin. It's not in CVS as it's not even remotely complete, but if you (or anyone else) wants to take a look I'll happily make it available. On my personal To-Do list, is a job to rip the old Migration Wizard out of pgAdmin I and make it a standalone application. This would have to be released under GPL as a number of people had a hand in that code. > Congrats with an otherwise very nice tool. Thanks, glad you like it. Regards, Dave.
Dave Page wrote: > 1) I wanted to redesign the Migration Wizard as it worked well for Access, > but not other DBs. > 2) The new design was based on the concept of building an object hierarchy > from the source database that could be modified in any way required before > building the target database. Data could then be filtered across though user > definable VB or JavaScripts (using the MS scripting Engine). Intriguing. I suppose this could take care of the problem I'm having in PgAdmin I with regional settings (need to change from e.g. Dutch to English, in order to correctly import e.g. single precision fields). > Currently I have the bginnings of a pgAdmin II Migration Wizard Plugin. It's > not in CVS as it's not even remotely complete, but if you (or anyone else) > wants to take a look I'll happily make it available. Sure ; no objection being a beta-tester. After all, isn't everyone ? :) However, as I am on the brink of converting a crucial MSAccess project to PostgreSQL, and not being an ODBC nor a pgSQL wizard, I'm understandably hesitant to convert my data with a pre-beta (?) tool. > On my personal To-Do list, is a job to rip the old Migration Wizard out of > pgAdmin I and make it a standalone application. This would have to be > released under GPL as a number of people had a hand in that code. So, I gather no "immediate" benefits are to be gathered from waiting for the PgAdminII Migration plug-in (as I've got this self-imposed 2001 deadline for the conversion) ? Actually, I wondered whether there would be any improvements wrt. the interaction with new pgSQL 7.2 features (ALTER TABLE ADD CONSTRAINT etc.). Kind regards, Didier Moens ----- RUG/VIB - Dept. Molecular Biology - Core IT tel ++32(9)2645309 fax ++32(9)2645348 http://www.dmb.rug.ac.be
> -----Original Message----- > From: Didier Moens [mailto:Didier.Moens@dmb001.rug.ac.be] > Sent: 12 November 2001 12:40 > To: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Status of Migration Wizard ? > > > Dave Page wrote: > > > > 1) I wanted to redesign the Migration Wizard as it worked well for > > Access, but not other DBs. > > 2) The new design was based on the concept of building an object > > hierarchy from the source database that could be modified > in any way > > required before building the target database. Data could then be > > filtered across though user definable VB or JavaScripts > (using the MS > > scripting Engine). > > > Intriguing. I suppose this could take care of the problem I'm > having in > PgAdmin I with regional settings (need to change from e.g. Dutch to > English, in order to correctly import e.g. single precision fields). > > > > Currently I have the bginnings of a pgAdmin II Migration Wizard > > Plugin. It's not in CVS as it's not even remotely complete, > but if you > > (or anyone else) wants to take a look I'll happily make it > available. > > > Sure ; no objection being a beta-tester. After all, isn't > everyone ? :) > > However, as I am on the brink of converting a crucial > MSAccess project > to PostgreSQL, and not being an ODBC nor a pgSQL wizard, I'm > understandably hesitant to convert my data with a pre-beta (?) tool. You misunderstand me I think. The code isn't even remotely beta, it barely even gets a list of columns in a table from the source database yet. I really have hit a total brick wall with this ODBC problem and don't have time to look at it right now (I'm in the middle of a large migration of an Informix database & IIS website to Linux). If you still want to look at the code then the offer is still there of course... > > > On my personal To-Do list, is a job to rip the old Migration Wizard > > out of pgAdmin I and make it a standalone application. This > would have > > to be released under GPL as a number of people had a hand in that > > code. > > > So, I gather no "immediate" benefits are to be gathered from > waiting for > the PgAdminII Migration plug-in (as I've got this self-imposed 2001 > deadline for the conversion) ? I doubt I'll even touch it this year. I'm not even sure my concept is possible using ODBC :-( > Actually, I wondered whether there would be any improvements wrt. the > interaction with new pgSQL 7.2 features (ALTER TABLE ADD > CONSTRAINT etc.). > It would be difficult to make direct comparisons as the new design concept is so completely different. In your case, I would suggest that you use pgAdmin I to migrate your data (http://gborg.postgresql.org/project/pgadmin). I hope to solve this problem, but I really don't know when I can right now :-( Regards, Dave.
Dave Page wrote: > >>-----Original Message----- >>From: Didier Moens [mailto:Didier.Moens@dmb001.rug.ac.be] >>Sent: 12 November 2001 12:40 >>To: pgadmin-support@postgresql.org >>Subject: Re: [pgadmin-support] Status of Migration Wizard ? [migrating MS-Access data in pgAdmin I/II] > It would be difficult to make direct comparisons as the new design concept > is so completely different. > > In your case, I would suggest that you use pgAdmin I to migrate your data > (http://gborg.postgresql.org/project/pgadmin). I hope to solve this problem, > but I really don't know when I can right now :-( Seems I'm stuck here. I've just installed PostgreSQL 7.2b3. As pgAdminII doesn't have a Migration Wizard, I'd have to use pgAdminI. Unfortunately, pgAdminI doesn't support pgSQL 7.2 (no OID's in pg_attributes ?). I suppose the only solution would be to revert to pgSQL 7.1, migrate my data to 7.1, dump and restore to 7.2, and then use pgAdminII ? Kind regards, Didier -- Didier Moens ----- RUG/VIB - Dept. Molecular Biology - Core IT tel ++32(9)2645309 fax ++32(9)2645348 http://www.dmb.rug.ac.be
> -----Original Message----- > From: Didier Moens [mailto:Didier.Moens@dmb001.rug.ac.be] > Sent: 05 December 2001 16:33 > To: Dave Page > Cc: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Status of Migration Wizard ? > > > Dave Page wrote: > > > > >>-----Original Message----- > >>From: Didier Moens [mailto:Didier.Moens@dmb001.rug.ac.be] > >>Sent: 12 November 2001 12:40 > >>To: pgadmin-support@postgresql.org > >>Subject: Re: [pgadmin-support] Status of Migration Wizard ? > > > [migrating MS-Access data in pgAdmin I/II] > > > > It would be difficult to make direct comparisons as the new > design concept > > is so completely different. > > > > In your case, I would suggest that you use pgAdmin I to > migrate your data > > (http://gborg.postgresql.org/project/pgadmin). I hope to > solve this problem, > > but I really don't know when I can right now :-( > > > Seems I'm stuck here. > > I've just installed PostgreSQL 7.2b3. As pgAdminII doesn't have a > Migration Wizard, I'd have to use pgAdminI. Unfortunately, pgAdminI > doesn't support pgSQL 7.2 (no OID's in pg_attributes ?). > > I suppose the only solution would be to revert to pgSQL 7.1, > migrate my > data to 7.1, dump and restore to 7.2, and then use pgAdminII ? > No, pgAdmin 1 will not work with PostgreSQL 7.2. I have since ported the Migration Wizard from it though into a pgAdmin II plugin. This can be found in the /binaries directory in the cvs at cvs.social-housing.org. Note that it's still under the gpl licence though. I was sure I emailled you when I did this :-( Regards, Dave.
Dave Page wrote: >>I've just installed PostgreSQL 7.2b3. As pgAdminII doesn't have a >>Migration Wizard, I'd have to use pgAdminI. Unfortunately, pgAdminI >>doesn't support pgSQL 7.2 (no OID's in pg_attributes ?). >> >>I suppose the only solution would be to revert to pgSQL 7.1, >>migrate my >>data to 7.1, dump and restore to 7.2, and then use pgAdminII ? >> >> > > No, pgAdmin 1 will not work with PostgreSQL 7.2. I have since ported the > Migration Wizard from it though into a pgAdmin II plugin. This can be found > in the /binaries directory in the cvs at cvs.social-housing.org. Note that > it's still under the gpl licence though. Works like a charm ! Two small hiccups with the Migration Wizard : 1. Under W2K and pgAdminII, I still experience a "reverse tab" (cursor moves to previous field instead of next field when pressing TAB). THis is the same behaviour as with WinME and pgAdminI ; 2. The Wizard defaults to the MS-Access system database as defined in the Jet registry settings : it would be nice if one could override this from within the Wizard (as per the "MS Access Workgroup Administrator", wrkgadm.exe). Thanks for a great piece of software. Kind regards, Didier Moens ----- RUG/VIB - Dept. Molecular Biology - Core IT tel ++32(9)2645309 fax ++32(9)2645348 http://www.dmb.rug.ac.be
> -----Original Message----- > From: Didier Moens [mailto:Didier.Moens@dmb001.rug.ac.be] > Sent: 13 December 2001 09:37 > To: Dave Page > Cc: pgadmin-support@postgresql.org > Subject: Re: [pgadmin-support] Status of Migration Wizard ? > > > Dave Page wrote: > > > >>I've just installed PostgreSQL 7.2b3. As pgAdminII doesn't have a > >>Migration Wizard, I'd have to use pgAdminI. Unfortunately, pgAdminI > >>doesn't support pgSQL 7.2 (no OID's in pg_attributes ?). > >> > >>I suppose the only solution would be to revert to pgSQL 7.1, > >>migrate my > >>data to 7.1, dump and restore to 7.2, and then use pgAdminII ? > >> > >> > > > > No, pgAdmin 1 will not work with PostgreSQL 7.2. I have > since ported > > the Migration Wizard from it though into a pgAdmin II > plugin. This can > > be found in the /binaries directory in the cvs at > > cvs.social-housing.org. Note that it's still under the gpl licence > > though. > > > Works like a charm ! Good! > > Two small hiccups with the Migration Wizard : > > 1. Under W2K and pgAdminII, I still experience a "reverse > tab" (cursor > moves to previous field instead of next field when pressing > TAB). THis > is the same behaviour as with WinME and pgAdminI ; Which fields - this should be easy to fix as it's only a tab order thing. > 2. The Wizard defaults to the MS-Access system database as defined in > the Jet registry settings : it would be nice if one could > override this > from within the Wizard (as per the "MS Access Workgroup > Administrator", > wrkgadm.exe). I'll add this to the todo list. > > Thanks for a great piece of software. Your welcome. Regards, Dave.
Dave Page wrote: >>Two small hiccups with the Migration Wizard : >> >>1. Under W2K and pgAdminII, I still experience a "reverse >>tab" (cursor >>moves to previous field instead of next field when pressing >>TAB). THis >>is the same behaviour as with WinME and pgAdminI ; >> > > Which fields - this should be easy to fix as it's only a tab order thing. Current order : 1. Database Type 2. Convert Column Names to Lower Case 3. Convert Table Names to Lower Case 4. Convert Index/Key Names to Lower Case 5. [Previous] 6. [Next] 7. [Migrate db] 8. Create Columns as 'NOT NULL' where applicable 9. Create Indexes on Migrated Tables 10. Create Primary Keys on Migrated Tables 11. Password 12. Username 13. .mdb File 14. [...] Correct order : 1-13-14-12-11-8-9-10-3-2-4-5-6-7 Regards, Didier Moens ----- RUG/VIB - Dept. Molecular Biology - Core IT tel ++32(9)2645309 fax ++32(9)2645348 http://www.dmb.rug.ac.be