On Fri, 8 Apr 2011 16:33:58 -0400, Kanwei Li <kan...@gmail.com> wrote:
> Hi Louise,
> 
> Have you considered doing a SQL dump and import? Sounds easier to me
> than writing a perl script ;)
> 
> -K

Oh yes I did... Yeah, that solution sounded so sweet that is was the first
thing I tried. But don't be fooled by the apparent easyness, it's another
whole ordeal to go through. If it was MySQL to MySQL or PSQL to PSQL, yeah
that would be the easiest and fastest way. But the syntax/structure used by
both is very different (MySQL is awfully non-standard), and there's no
batteries-included way to do the translation, just a few scripts here and
there. You have to edit stuff manually anyway.

An example: everywhere I see people giving the --compatible=postgresql
option of mysqldump as the obvious solution of all problems, but when I
tried it and searched about it, I really wondered why they provide this
option at all. If you want more information about it you should check this
website out:
http://en.wikibooks.org/wiki/Converting_MySQL_to_PostgreSQL

When I saw the mess it was, I told myself that since the tables are
automatically generated, I might as well make the most of it and only
transfer the data. I tried using Kettle:
http://pinoytech.org/question/5417386/import-mysql-dump-to-postgresql-database
but in the end I got job crashes and error message like "something
crashed, period" so since I didn't want to waste too much time on trying to
make this steam machine work, I'd rather make my own lil' script. Yeah, in
the end, it was the easiest way to me, believe me or not. ^^

Cheers ;)
L-A

___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/

Reply via email to