On Fri, Sep 29, 2000 at 06:47:48PM +0200, [EMAIL PROTECTED] wrote:
>
> 1) At this stage it looks like the codebase is still going to be quite
> tightly coupled to MySQL, as that's what we use, and we haven't come
> up with a decent plan to do otherwise. If anyone would like to make any
> suggestions on this front before we do too much of this, we're love to
> hear them. (There was quite a lot of talking about this at the conference,
> but I'm not really sure if anything decent came out of it!)
For starters, MySQL is now GPL'd, which makes it kosher for open source
projects.
For seconds, a similar problem arose at DataCash: big application is
tied to one RDBMS (mSQL) and needs to be untied. The solution was to
build a DBI proxy module that could be use'd instead of DBI::mSQL;
this could be configured to open a connection to J. Random Database
instead of MySQL and as long as said RDBMS supported the functions or
syntax being used it ensured that not one line of code (other than the
use statements) needed to be changed in the main application. This
allowed a painless port from mSQL to MySQL, _and_ successful trials
with Oracle and Interbase using the same code. A more ambitious
proxy layer would also do some translation of MySQL functions into
their equivalents in whatever other database was required, but that
might be unneccessary.
In any event, the idea of contributing a solid online shop to the
community is a *very* good one and deserves general applause.
-- Charlie
