RE: MySQL -> pgsql

From: KuroiNeko <evpopkov(at)carrier(dot)kiev(dot)ua>
To: pgsql-general(at)postgresql(dot)org
Subject: RE: MySQL -> pgsql
Date: 2000-10-19 21:37:43
Message-ID: 39EF69A7.nail7X11G7CX@ed.ed
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Conversion tools? Na, that's just a small part of what I do.

Since it's a network monitor, chances are you're not using exotic
datatypes incompatible, or non-existant in PGSQL? If so, the fastest way
would be to get a `dump' schema + data script from MySQL and adjust it with
sed or PERL where it's required.
On the other hand, just porting the tables is probably not what you want.
This will remain MySQL, only executed by PGSQL: no DRI, no rules, no
triggers, nothing. Probably it's worth designing the schema from scratch,
using natural features of PGSQL and work out migration procedures then?
Not knowing exactly what data you operate it's hard to tell more.

--

Well I tried to be meek
And I have tried to be mild
But I spat like a woman
And I sulked like a child
I have lived behind the walls
That have made me alone
Striven for peace
Which I never have known

Dire Straits, Brothers In Arms, The Man's Too Strong (Knopfler)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-10-19 21:42:19 Re: prefer (+) oracle notation
Previous Message Neil Conway 2000-10-19 21:30:14 Re: MySQL -> pgsql