ViSolve DB Team wrote: > Hi, > >> From MySQL 4.1, there is a support for mysqldump --compatible option. > There is a safe/cool dump for your table: > Try lik: > shell > mysqldump -u dev -p visolvetestdb credits > --compatible=postgresql > /home/test/ps.sql > > And also, > By default tables are dumped in a format optimized for MySQL. > Legal modes are: ansi, mysql323, mysql40, postgresql, oracle, mssql, > db2, maxdb, no_key_options, no_table_options, no_field_options. One can > use several modes separated by commas.
Safe/cool? I don't understand all of the options you've used on this command but I can tell you that I did something similar to: mysqldump --compatible=postgres > dumpfile.sql Unfortunately, this does not seem to result in a file that Postgres can use directly. I'm having to mess with every single line just to get my data in. This is a *real* pain since I'm not really very experienced with either Postgres or MySQL. It's cost me a weeks work already. It's fortunate that we planned for this kind of thing. Jim C.
signature.asc
Description: OpenPGP digital signature
