From: | "Van Ingen, Lane" <lvaningen(at)ESNCC(dot)com> |
---|---|
To: | "Sean Davis" <sdavis2(at)mail(dot)nih(dot)gov>, "Glauter Moulin Coelho" <gerente(at)gerente(dot)com(dot)br> |
Cc: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Migration from MySQL |
Date: | 2005-05-25 17:19:12 |
Message-ID: | A3FF4275060B76459B5C08A64AE330C805C3B3@twmail.esncc.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
I attached a checklist of items that we found had to be addressed when we converted from MySQL to PostgreSQL. Some of these concern the data itself, not just the schema.
I don't know if SQL::Translator does all of this; if not, hope it helps you out! Some of the items in the list are the way we handled things here, so use or ignore those.
-----Original Message-----
From: pgsql-novice-owner(at)postgresql(dot)org on behalf of Sean Davis
Sent: Wed 5/25/2005 11:45 AM
To: Glauter Moulin Coelho
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: [NOVICE] Migration from MySQL
On May 25, 2005, at 10:40 AM, Glauter Moulin Coelho wrote:
> Hi,
>
> Does anyone knows some tool to migrate data from MySQL to PostgreSQL
> WIN ?
>
> Regards.
Look at SQL::Translator, a perl module for migrating schema.
Sean
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
Attachment | Content-Type | Size |
---|---|---|
MySQL to PostgreSQL Conversion Rules.doc | application/msword | 25.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Glauter Moulin Coelho | 2005-05-25 17:29:29 | Re: Migration from MySQL |
Previous Message | Volkan YAZICI | 2005-05-25 17:17:53 | Re: Migration from MySQL |