From: | Mimiko <vbvbrj(at)gmail(dot)com> |
---|---|
To: | Posthresql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgres driver for mysql |
Date: | 2016-09-11 11:35:25 |
Message-ID: | 73d8266b-297f-5cb1-c6a2-48cc2d60eb53@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05.09.2016 22:42, Adrian Klaver wrote:
> The only thing I know of is the other way around:
>
> https://wiki.postgresql.org/wiki/Fdw
>
> Trying to figure out how
>
> 1) "I want to move applications to postgres."
>
> and
>
> 2) "Changing applications is impossible, they are proprietary and work
> only with specific databases only. "
>
> is going to work out?
>
Hi.
This is interesting, but apps needs different mysql versions. So DB will
pe sparse and inconsistent. But this solution is great if apps can be
moved to postgres, but DB cannot be move from mysql. Can't the data be
moved also? Well. Your solution is the the over way. But thank you for
info about this.
On 06.09.2016 12:03, Glyn Astill wrote:
>
> I've no answer to your question really, however it looks like at some
point a while back I bookmarked this page:
>
>
http://www.pinaraf.info/2013/03/my-post-engine-a-postgres-engine-for-mysql/
>
> Is that what you were using? If so the git repository is still
accessible via gitweb:
>
>
> https://www.gitorious.org/my-post-engine/my-post-engine
>
> If you're desperate to use it you could pull a snapshot from there.
Yes, this was the page I was looking for. Especially link to source
repository. Wish it was maintained. Thank you.
From | Date | Subject | |
---|---|---|---|
Next Message | Christian Convey | 2016-09-11 13:47:10 | Re: C++ port of Postgres |
Previous Message | Patrick B | 2016-09-11 09:26:42 | Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2 |