On Wednesday 13 June 2007 10:18:44 Berner Martin wrote: > Hello > Dos someone have already do a migration of the Catalogue from a PostgreSQL > to y MySQL? Or know how it has to work? I tried to dump Postgres so that he > dump only the Data and use INSERT in stead of COPY. Then I grep only the > lines with Inserts. I create the bacula-tables with the script > (make_mysql_tables) and try to insert the Data dumped from Postgres. But > the Tables in MySQL seams to have different Names then in PostgreSQL at > lest different upper/lower case. > > thanks for any help > > Berner Martin
I don't see any way to get past the case sensitivity problem, except by replacing all table names with their mysql versions in the dump (a simple perl or sed script will do the trick) But I feel I should ask : maybe you don't really need to leave postgresql ? What I really mean is that if it's for performance reasons, things will definitely get better with the next bacula release (on par or even better than mysql), with the batch insert code. If it's because you're more at ease with mysql or some other good reason of this kind, forget what I've just said. Both database have their advantages... ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
