I don't know your project's context or background, but have you considered
porting to PostgreSQL (www.postgresql.org)? It's also Open Source with a
BSD-style license, and is much more comparable to Oracle than is MySQL. It has
full support for views, triggers, functions, subqueries, user-defined datatypes,
and very strong support for SQL92 syntax as well. The date functions are
extensive, though I don't know how they compare with Oracle's in terms of
syntax.
To answer your actual question, I haven't heard of a parser that converts a SQL
statement from one database platform to another. There are abstraction layers
like DBI and Alzabo, but I don't think those are what you mean. The best answer
I've found so far is to stick with standard SQL as much as possible, and don't
switch databases in mid-project if I can at all help it. :-)
--Wes Sheldahl
Maria Quinn <[EMAIL PROTECTED]> on 08/29/2001 07:50:53
AM
To: dbi-users <[EMAIL PROTECTED]>
cc: (bcc: Wesley Sheldahl/Lex/Lexmark)
Subject: Porting from Oracle to MySQL
I've got an application developed using DBI, Oracle, and CGI. It works well
on this platform, but now I'm faced with the prospect or getting it to run
with a MySQL back end instead of Oracle. The differences between the two
implementations of SQL (especially date functions) are causing some problems,
and I've been thinking of writing some kind of parser that takes an SQL
statement in one flavour and converts it to the other. I was wondering if
anyone had done this kind of thing before. Am I reinventing someone else's
wheel, or barking up the wrong tree? I can't help feeling that there
must be tools to deal with this kind of thing already.
Thanks in advance,
Maria
