From 22c0e7d349629353e80d1a9f79c4d1b6376e293a Mon Sep 17 00:00:00 2001 From: Dimitri Fontaine Date: Sun, 9 Apr 2017 13:28:33 +0200 Subject: [PATCH] Include a link to pgloader This script has a very good Google rank for migrating from MySQL to PostgreSQL and seems to be quite dedicated to a specific environment and migration project. Pgloader (https://github.com/dimitri/pgloader) solves the generic problem and work directly from a MySQL connection, you can run it in your CI environment until you're ready to switch in production. As pgloader author, it seems to me that linking the project from your README would be valuable for the both of us, allowing you to focus on your context and helping the general case being better covered. --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index f475c41..d09504b 100644 --- a/README.md +++ b/README.md @@ -8,6 +8,13 @@ notably, it doubles the lengths of VARCHARs due to a unicode size problem we had, places indexes on all foreign keys, and presumes you're using Django for column typing purposes. +For a more general approach have a look at pgloader , +which connects to a running MySQL instance and discovers the schema from the catalogs to +then reproduce it in PostgreSQL with a default set of casting rules (that you can edit). +[pgloader](https://github.com/dimitri/pgloader) supports migrating the schema and the data, +converting data on the fly, and reproducing Not Null constraints, default values, primary +and secondary indexes, foreign keys and comments. + How to use ----------