Skip site navigation (1) Skip section navigation (2)

Re: Migration from MySQL to PostgreSQL : Datatypes?

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: Migration from MySQL to PostgreSQL : Datatypes?
Date: 2010-12-25 07:17:04
Message-ID: if45pg$bp2$ (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
On 2010-12-23, Bill P. <maxarbos(at)yahoo(dot)com> wrote:
> --0-1401805872-1293124338=:85107
> Content-Type: text/plain; charset=us-ascii
> Hello,
> What would be the best way to deal with migrating a database structure and data 
> from a mysql db to postgres when there are dataypes in the mysql tables that are 
> not present, and thus throw errors using the current migration wizard, in 
> postgres?
> If i leave these few tables out on first import, many of the other tables that 
> these few key back to dont get created either.
> I found a program called easyfrom, but it's over $200 and only runs on windows. 
> Navicat, which i have, doesnt seem to have any provision to change the datatypes 
> on structure sync from one to the other types of db.
> Any suggestions would be great.
> thanks.

when I had to migrate an (mdbtools) Access dump. I was able to do all
that was needed using sed.  

(But if you don't speak regex that's probably not going to work for
you, it should be equally possible with any general purpose
programming language)

Is there any sort of guarantee, for that $200 tool, paying for it 
might be better than reinventing your own.  That translator will
probably work fine under wine. Ask the vendor, if they don't know,
offer to test it for them: you might get a discount!

⚂⚃ 100% natural

In response to


pgsql-novice by date

Next:From: thewhitelanternDate: 2010-12-25 15:10:14
Subject: in PostgreSQL 9.0.2 / pgAdmin III - ERROR: relation "[table name]" already exists
Previous:From: Benjamin GolderDate: 2010-12-24 07:42:12
Subject: Re: super beginner setting up postgresql for the first time

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group