Re: [Proposal] DB_OO

I had a brief look though, In general ++ Major feature additions above DataObjects + the proxy creation of objects on the fly. (I will implement this...... promise), however, I doubt it will be by creating class def's on the fly, as this makes debuging and program reading v.difficult (eg. where is that class/method xxxx defined????) + richer dataformat this is something that the MDB schema is getting close to perfecting?? :), and should really be the way to go. * most of the methods are just 'different' names, and do pretty similar things. It seemed a little more complex internally, in terms of 4 classes doing what 1 or 2 do currently in DataObject. other than the proxy creation, I doubt it would take more than 30 mins, to write a Wrapper to DO, to implement that API....? funnyly enough, DB_DataObjects was originally called DB_oo, when it started over 2 years ago. It would be worth looking at dataObjects, it would not take long to make a wrapper for your older code to use it, and It would make alot of sense to replicate some of the proxying stuff in DB_DataObject::factory() & the generator. Regards Alan Sérgio Carvalho wrote:

DB_OO is a package for simple object oriented database abstraction. It has been in production use for about two years now. I believe it would be interesting to have it part of PEAR. Tutorial and documentation can be found here: http://pear.sergiocarvalho.com/docs/DB_OO-1.0/ Source files can be found here: http://pear.sergiocarvalho.com/docs/DB_OO-1.0/source/ And the package can be installed using: pear install http://pear.sergiocarvalho.com/DB_OO Description ----------- The package generates proxy classes for a Database Abstraction Layer, that represent database tables. Class generation is fully automatic, deduced from metadata present in the RDBMS system catalog. It aims at imposing little to no overhead on the developer, while fulfilling the simplest 80% of operations without any SQL present in the application code. The domain of usage overlaps that of DB_Dataobjects but is not exactly the same. While DB_Dataobjects is building up to be the equivalent of Castor (http://www.castor.org/) for PHP, DB_OO has no pretention of providing features like table joins, field validation or form generation. Instead, the option is made for simplicity of use, which obviously limits the range of features that can be implemented. With the release of this code in GPL, and exposure to the PEAR community, I am hoping to gather developer support for databases other than PostgreSQL and Mysql. I also expect to have the most recently supported database code (mysql) more thoroughly tested. I'm using this package on several of my own commercial projects, so maintaining support is a non-issue. Cheers, Sérgio Carvalho --------------- Portugalmail Multimédia, Lda http://www.portugalmail.pt/

-- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com