From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | "Sean Davis" <sdavis2(at)mail(dot)nih(dot)gov> |
Cc: | pgsql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: MySQL to Postgresql schema conversion |
Date: | 2008-09-30 17:18:52 |
Message-ID: | b42b73150809301018m3f9088bfo8df57b93811ba0ae@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 30, 2008 at 12:48 PM, Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> wrote:
> On Tue, Sep 30, 2008 at 10:08 AM, Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> wrote:
>> There are a number of mysql to postgresql converters available, but
>> many of them have significant shortcomings. Has anyone found a tool
>> that works well? I am trying to convert a couple of relatively large,
>> public schema to postgresql.
>
> I started playing with sqlalchemy (python) which can reflect a schema
> to python objects. Those objects can then be used to instantiate
> another schema in a different database dialect. Works like a charm
> after modifying a couple of column names. It mirrors about 4000
> tables in about 45 seconds (of course, without the data).
Does it get all the various constraints and stuff (if any)? Simple
field to field copy techniques only tends to work if the database only
uses a small subset of common features. Great for you if it works
though.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Davis | 2008-09-30 17:37:19 | Re: MySQL to Postgresql schema conversion |
Previous Message | Sean Davis | 2008-09-30 16:48:09 | Re: MySQL to Postgresql schema conversion |