PEAR DB and ADO+

Hi Manuel, Some preamble first. Many high performance dynamic websites make extensive use of caching data from the database in order to scale, so that a server farm can be serviced by one database server. In most PHP database wrapper libraries, the caching is not integrated into the library, but done by some other program, eg: Session variables or PEAR Cache. Now suppose the user is viewing the recordset in a html table and wants to reorder the data by some criteria. Our database wrapper libraries normally do not have the ability to resort the cached recordset, so we have to query the database with a new ORDER BY criteria. Here's why ADO and ADO+ is so cool. ADO/ADO+ has a built-in database engine so you don't have to call the actual database server (mysql or oracle etc) to do the sort! Similarly, ADO and ADO+ has filtering capabilities so we don't have to requery the server for Searches also. An ADO+ recordset is XML based with a DTD so ADO+ is self-documenting, and we can simulate ADO+ recordsets on non-Microsoft platforms. So just as ADODB database wrapper library is a bridge for ASP programmers to migrate to PHP, having ADO+ recordset support in Metabase/PEAR/ADODB would be a bridge for .NET programmers to move to PHP. Regards, John > Hello > > John Lim wrote: > > Seriously, people should look at what Microsoft is doing with > > Microsoft.NET and their ADO+ classes. Beats PEAR DB and many other > > database wrappers (including the one I wrote, ADODB) in strength and > > power. Microsoft have a lot of experience with database wrappers, eg. > > ODBC, ADO, RDO, etc. Some of them were failures, but the work was always > > interesting. > > Honestly, I could not see exactly what ADO+ beats what any of the PHP > database wrappers do. Would you care to provide examples? > > Manuel Lemos