RE: [PEAR-DEV] Re: [PHP-DEV] Advice on design issues (long)...

> > I have not checked into dbx was much was I wanted (or should), but I > > have heard that he is also moving forward. > he _is_ moving forward. Slowly, though :-) But then again, if somebody really wants an extra driver/wrapper, just point me to the where I can find the database app and I can add it in a couple of hours... > same limitations also apply to dbx, since it builds directly > on the current extensions. Yeah. I figured it would be easier to just wrap the current extensions and present one unified api. I've got some extra plans for the api, but that will still have the same limitations. Problem is, there is so much userland code out there, you can never remove the existing extensions. That means that whatever db-abstraction module is written, it will always live alongside all the other db-extensions. The only way to slowly move towards one db-api is when PHP officially adopts the api, the manual is changed to represent this (including all examples) etc. That way new userland code will use this db-api first, instead of trying the mysql extension (or whichever db is appropriate) directly... Cheerio, Marc.