Re: Migrate from MySQL to PostgreSQL

Hi Lukas! Lukas Smith wrote: > MDB does support reverse engineering MySQL databases into the xml > schema format. There is a script as part of the MDB install called > reverse_engineer_schema.php or something like that. However note that > this functionality is focused on mapping all of the databases to MDB > datatypes. In case it cant do that 1-1 it will issue warnings you can > fix manually. The result will be an xml schema file which you can then > use to create the database in pgsql. Thanks a lot. I will have a look at this. After a whole night of trying to convert the table-definitions by hand, I think I understood the advantage of MDB ;-) I know that I will have to do this also for Oracle, DB2 and MSSQL. And I know that some things in my Data-Definitions will change in future, and I will have to add more tables. As said before I'm using PEAR::DB in my application, does it make sense zu switch to MDB? I Think there will be some changes necessary, right? And MDB was slower than DB, wasn't it? But that is not so important, but for example there is no ODBC driver for MDB, and I need ODBC für BD2 (perhaps I could write one and give it to you?). And there are missing some other packages, for example I am using DB_Pager, which only works with DB, or perhaps I want to try DB_DataObject, which also is only available for DB. ` Is there any advantage of using MDB instead of DB in my application itself (only SELECT, INSERT, UPDATE) ? So I think if it would be a better idea to leave my application using DB, and use MDB for creating and changing table-definitions in XML, and update the definitions in the database using MDB fuctions. What would you suggest? What about MDB2? I have read that it would be better than MDB, but what is better here? And when will it reach"stable"? Is there any advantage for me using MDB2? Or should I later switch fom MDB to MDB2? Thanks for your answer. kind regards Andreas