From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | kevin(at)valenfor(dot)com, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Database conversion woes... |
Date: | 2004-02-03 19:29:52 |
Message-ID: | 200402031929.52383.dev@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tuesday 03 February 2004 16:42, Kevin Carpenter wrote:
>
> Thanks in advance, will give more detail - just looking for some open
> directions and maybe some kicks to fuel my thought in other areas.
I've taken to doing a lot of my data manipulation (version conversions etc) in
PG even if the final resting place is MySQL.
It's generally not too difficult to transfer data but you will have problems
with MySQL's more "relaxed attitude" to data types (things like all-zero
timestamps). I tend to write a script to tidy the data before export, and
repeatedly restore from backup until the script corrects all problems.Not
sure how convenient that'll be with dozens of gigs of data. Might be
practical to start with the smaller databases, let your script grow in
capabilities before importing the larger ones.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2004-02-03 19:59:04 | Re: Database conversion woes... |
Previous Message | Josh Berkus | 2004-02-03 19:01:57 | Re: Database conversion woes... |