[wp-hackers] alternative database support

[Michael K. Dolan Jr.]

I thought it was #1 - it makes sense to find at least some semblance of 
continuity if a port is made though to push some of the code changes 
back into the mainline if possible which is where I think everyone is 
jumping to #2...


Alex King wrote:
> Sorry to keep bringing this up, but it's obviously unclear from the 
> resulting e-mails in the thread:
>
> Is this discussion about:
>
> 1.) the best way for people who are *already* going to port WP to 
> another db to work together on a fork of some kind by building a $wpdb 
> replacement and seeing whatever else they need to do[*]?
>
> 2.) changing WP to officially support ADOdb?
>
> I was sure it was #1, yet folks keep popping up to explain why #2 is a 
> bad idea so maybe I have it wrong.
>
> [*] Changing the string escaping and dates in all queries will be 
> required for ADOdb.
>
> Cheers,
> --Alex
>
> Personal   http://alexking.org
> Business   http://kingdesign.net
>
>
> On Oct 10, 2006, at 5:24 AM, Robert Deaton wrote:
>
>> Here's a summary of all the reasons why I think this is a bad idea.
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
>