RE: [PEAR-DEV] [Proposal] DB_OO

> From: Sérgio Carvalho [mailto:sergio.carvalho@portugalmail.com] > Sent: Monday, December 22, 2003 5:34 PM > Description > ----------- > 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. What is the benefit if limiting the scope? I mean why cant you just not use the " features like table joins, field validation"? > 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. GPL is not compatible with PHP userland code as this would result in licensing issues with all closed source code that might be distributed along with any GPL'ed userland code. Therefore we only allow LGPL, PHP, BSD and similar licenses into PEAR. Finally I think we have that area covered fairly well with DataObjects and QueryTool. You will have to make it more clear how your packages differentiates itself from these classes and why any missing features cannot be added to these packages. Please also look at the recent thread on DB_Simple as this seems addresses a similar subsection of the PEAR package repository. Regards, Lukas