From: | Chris Travers <chris(at)travelamericas(dot)com> |
---|---|
To: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, PostgreSQL advocacy <pgsql-advocacy(at)postgresql(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | MySQL to PostgreSQL, was ENUM type |
Date: | 2005-07-27 20:13:26 |
Message-ID: | 42E7EAE6.1000001@travelamericas.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general |
So, it seems to me that there is a fair bit of work to be done on
helping people migrate MySQL to PostgreSQL.
So far, the checklist I can see includes:
* Maintaining conversion scripts
* Reviewing pain points and looking at ways of mitigating them.
* Building solid migration documentation
* Providing porting frameworks
This last item could have some potentials. For example, a source-code
compatible library to map MySQL client lib system calls to libpq
operations for the C API, PHP wrapper scripts, etc.
My company will be providing a PHP wrapper script, and will be working
on some documentation. Most of the documentation will be BSD-style
licensed with the exception of the references to my company's services
(which must be stripped out of non-verbatim reproductions).
If anyone else sees any other interesting areas that need work, it might
be worthwhile to discuss them as well.
Best Wishes,
Chris Travers
Metatron Technology Consulting
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-07-27 22:58:41 | Re: [Fwd: DEADLINE LinuxWorld Expo 2005 .Org |
Previous Message | Peter Eisentraut | 2005-07-27 18:05:22 | Re: [HACKERS] Enticing interns to PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2005-07-27 20:14:13 | Re: DELETE with JOIN syntax |
Previous Message | Eric Davies | 2005-07-27 19:59:22 | link errors building extensions for Postgres on Windows using MinGW |