From: Kevin <kevin@valenfor.com>
To: pgsql-performance@postgresql.org
Subject: Database conversion woes...
Date: Tue, 03 Feb 2004 15:29:41 -0700
Message-ID: <402020D5.2050902@valenfor.com> (raw)
First just wanted to say thank you all for the quick and helpful
answers. With all the input I know I am on the right track. With that
in mind I created a perl script to do my migrations and to do it based
on moving from a db name to a schema name. I had done alot of the
reading on converting based on the miss match of data types that MySQL
likes to use. I must say it is VERY nice having a intelligent system
that say won't let a date of '0000-00-00' be entered. Luckily I didn't
have to deal with any enumerations.
So the conversion goes on. I will definitely be back and forth in here
as I get the new queries written and start migrating all I can back into
the pg backend using plpgsql or c for the stored procedures where
required. The mammoth replicator has been working well. I had tried
the pgsql-r and had limited success with it, and dbmirror was just
taking to long having to do 4 db transactions just to mirror one
command. I have eserv but was never really a java kind of guy.
Alright then - back to my code. Again thanks for the help and info.
Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: kevin@valenfor.com
Subject: Re: Database conversion woes...
In-Reply-To: <402020D5.2050902@valenfor.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox