[wp-hackers] alternative database support

[Peter Westwood]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex King wrote:
> Forking is part of Open Source - if the core product is (for whatever
> reason) not willing to satisfy needs/requests that people have, they can
> choose to do so themselves. You may not like this and/or disagree with
> what they are talking about doing - that is your right.
> 
> All I'm saying is that if the folks that want PostgreSQL/SQLite/etc. all
> work together on an ADOdb port, this work can benefit and be leverages
> by others. I think that having a single fork around additional database
> support is a lot better idea than a fork for each database type.
> 

Surely the best thing is to try and work with the support that is there.

Try and write a port to another db that uses the ability in 2.1 to
replace wpdb with a different version without changing and WordPress code.

Write the new wpdb such that it translates the queries and deals with
the mysqlisms.

If this can't be done without any changes to the core code them submit
them as small simple well reasoned patches to trac - if they improve
WordPress and help the ability to integrate in on other dbs then they
will likely get into the core code.

By doing it this way and creating a "plugin" to get the alternative db
support in you can concentrate on one thing - db independance rather
than ending up with a db independant old version which doesn't lend
itself to merging back in.

westi
- --
Peter Westwood
http://blog.ftwr.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFLAggVPRdzag0AcURAhvZAKCoJMGbaFp8Mp6iAgJ+XMfFXagxxwCeIPhs
/pT9Ec7w/lk9O314L2p/cgI=
=J57V
-----END PGP SIGNATURE-----