Re: portability Oracle <=> MySQL

[Roland Bouman]

Hi,

just download the migration toolkit from the mysql download page - this should cover the oracle to mysql migration (but you will have to take care of the packages and triggers and procedures yourself)

If I were to create a portable solution I'd:

-use ansi datatypes. No more NUMBER, no more VARCHAR2 in Oracle; No more ENUM, no more SET in mysql
-use plain sql as much as possible - at present, plain sql is much better portable than procedures
- use the innodb engine for tables, and the strict sqlmode

An alternative would be to set up a repository that describes you application in terms of abstract datatypes etc, and use templates or reports to generate platform specific code. Then, you are free to use procedures etc - as long as you can store it inside the repository in a sufficiently open format.

For the relational structures, this is hardly a problem but it can be for the code bits (triggers, procs etc). You could for example use some XML format and use XSLT to generate platform specific code.

The latter method will cost you lots of work, and is only useful if you plan on building/maintaining several apps for different platforms for an extended period of time.



Edited 1 time(s). Last edit at 02/28/2006 06:58PM by Roland Bouman.