Comments Inline:
But I'm very surprised by the class db_oo. It seems to be excellent (when i
look to the examples).
Very nice class indeed. I could share some code to add AND/OR SQL
(see TODO)
functionality. My fear with that classes is the support for JOIN/UNIONs,
do that class support them?
I did start looking at this - its under the db_oo_crosstable, however It got to the point where the simplicity of using this type of data modelling was kind of lost when you start working with JOINS/UNIONS - it was just easier to go back to hard coded SQL for a join query...., (which can be supported - see db_oo::query in additional methods
even alot of the 'additional features for queries' could be described as an overkill, however it's always a fine balance (if you are building a query from mutiple conditions of a form input - eg. sort by..., only show date range..... it works well
Why is this class not in PEAR CVS ??? Why is this
class not in PEAR packages ???
Alan is always welcome to suggest the class for being part of PEAR and
get his CVS account if he already don't have one :)
There are a number of questions that need answering before it goes in PEAR:
Name? - having looked at JDO (Java Data Objects), it almost be cheeky to call it PBDO (Php DataBase Object) as it appears to do alot of similar thing.. - I'm game for ideas..
DB_OO
DB_Object
DB_PDO
DB_DataObjects (I quite like this...)
My only other thought was that there is/and will be more than one way to skin a cat - eg. it is extremely likly that somebody else will come up with another query builder that is just as original/usefull in the future, using different concepts. - the naming should enable that to be added in without too many namespace issues.
(once thats decided, if you give alan_k karma for the PEAR tree I can add it in)
There are still a few TODO's on it.
1. stop using $__vars and __methods -> single underscores
2. order_by -> orderBy()
3. look at using static methods and static vars to store some of the current global vars.
4. look at PEAR debugging rather than it's current effort.
5. look at adding PEAR::Error support
6. Figure how to do the out the package file..
7. double check on some method names - condition_append() -> whereAnd() and whereOr()
regards
alan
Is there a roadmap for PEAR (Thinks to do...)
?
There is a TODO file under the pear/ module. Note that is only related
to the infrastucture, not the classes as that is a matter of the author.
BTW I remember someone wanting to implement this functionally for the
PEAR Web.
And who decides to add a new package or even a new cvs account ?
We in pear-dev. I recommend you to read the FAQ at
http://pear.php.net/faq.php.
Tomas V.V.Cox