Tag Info

Hot answers tagged


Here are a few open source tools, that can be very helpful: FromMySqlToPostgreSql is a feature-reach tool and very easy to use. It maps data-types, migrates constraints, indexes, PKs and FKs exactly as they were in your MySQL db. Under the hood it uses PostgreSQL COPY, so data transfer is very fast. FromMySqlToPostgreSql written in PHP (>= 5.4). pgloader ...


You can use EnterpriseDB Migration Wizard, for example. It can symply migrate OracleDB. But for Mysql, it has some limitations, for example, it not supports views, triggers, stored procedures. For more, see EDB Migration Toolkit. Not sure, but it can be possible to migrate mysql->oracle->postgresql saving your stored procedures (in case they exists). ...


Dumping subsets of table data can only be done backing up individual tables. I once answered a post entitled Is it possible to mysqldump a subset of a database required to reproduce a query?. In that post, I used mysqldump strictly against the tables in question. The only thing you can do is to produce two dumps mysqldump of the database without table1 ...


That is a default option in mysqldump. As the name states it only disables the foreign key check, which is necessary. If you don't disable the check, you'll almost certainly run into foreign keys errors, unless the restore, coincidentally, honors the parent/child relationships in the sequence that it restored the tables in. Extremely unlikely. Mysqldump ...


I had to do a little digging in the source code of mydumper to find the answer to this question. If you look at the actual source code of mydumper: You will find the following starting on line 415 as part of the process queue: if(use_savepoints && mysql_query(thrconn, "SET SQL_LOG_BIN = 0")){ g_critical("Failed to disable binlog for the thread: ...


This is just to add to the existing answers, which helped me find this solution. I used FromMySqlToPostgreSql. All you need to do is to download and extract FromMySqlToPostgreSql, make a copy of the sample config file, set the db connection values in it, and run the index file with the following command: php index.php config.xml Simple yet effective!


The behaviour is correct and it is incorrectly observed as per update from the questioner. This got verified by further debugging the dumpload adding a debugging select syntax after the erroneous SQL in the dump.

Only top voted, non community-wiki answers of a minimum length are eligible