From: | "Shoaib Mir" <shoaibmir(at)gmail(dot)com> |
---|---|
To: | "Michael Fuhr" <mike(at)fuhr(dot)org> |
Cc: | "Brendon Gleeson" <brendon(at)gleesonprop(dot)co(dot)za>, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Testing / debuging data import |
Date: | 2006-10-04 19:50:13 |
Message-ID: | bf54be870610041250w77c66afw36b78b21128a27a8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
There is this open source tool "mysql2psql" which is bascially a Perl script
that can take as an input MySQL dump file and covnert that to a PostgreSQL
specific dump file so that you can restore the dump file easily in
PostgreSQL.
You can find the tool at -->
http://gborg.postgresql.org/project/mysql2psql/projdisplay.php
Thanks,
----
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)
On 10/4/06, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
>
> On Wed, Oct 04, 2006 at 09:03:50AM +0200, Brendon Gleeson wrote:
> > Basically what I want to do is simulate a data import (from a file with
> > full insert statements and no table creation), I want the offending
> > record/line to be printed to stdout with a verbose / helpful error.
>
> This doesn't quite meet your requirements, but have you looked at
> pgloader?
>
> http://pgfoundry.org/projects/pgloader/
>
> --
> Michael Fuhr
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2006-10-04 21:18:00 | postgresql db account |
Previous Message | Guy Rouillier | 2006-10-04 19:46:16 | Re: Potentially annoying question about date ranges (part 2) |