Re: [OT] MySQL is bad, but THIS bad?

On Thu, 18 May 2006, Joshua D. Drake wrote:

> I understand the idea but I personally don't like it. I am not really
> interested in cross-database compatible code. 9 times out of 10 it is
> hacky, slow and lacks a solid supportable model because you are always
> taking into account *the other* databases the application supports.

I don't disagree about the 'hacky, slow and lacks ...' ... but, there are
alot of MySQL based apps out there that are just *way too big* to convert
wholesale to PostgreSQL that, in all honesty, are better suited to
PostgreSQL ...

To give someone a running chance at migrating it to PostgreSQL, a 'MySQL
compatibility module' would allow them to just plug the existing DB in,
and then work at improving sections of the code over time ...

Hell, if done well, the module should be able to dump appropriately
'clean' PgSQL schemas ... as in your example elow about the domains ...

something like:

postgres=# create domain varchar2 AS text;
CREATE DOMAIN
postgres=# create table test ( mytext varchar2 );

should dump out to:

create tabel test ( mytext text );

So, developer would be able to load the MySQL schema and run the
application, but would also be able to improve the code in the application
and dump out a PgSQL clean schema so that the next person, in theory,
wouldn't even need the MySQL module ...

the point isn't whether or not MySQL is a competitor ... the point is that
there are *alot* of MySQL based applications out there that are a major
PITA to convert (or get converted) all at once ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664