Re: DB_QueryTool or DB_DataObject?

It's worth noting that other than the query building side, one of the core design ideas behind dataobjects is to try put all your table orientated code into the extended dataobject class - rather than splattering it around the application. Then provide a consistant base level API for each table. query building is kind of a secondary (Albeit essential) task of dataobjects. Current Plans for dataobjects: - A matching (or similar) LDAP_DataObject (which is just about complete) - investigation of overload extentions to see if generator could make use of this ,as I mentioned to somebody recently, PHP is designed to do C# like overloaded variable settings, rather than getter/setters.. (as there is a significant speed penalty if you use methods for all variable access) - use of PHP5 privates for the really private stuff. - use of PHP5 object statics for all the nasty global hacks. - replacement of @ code with isset() and real tests. (underway) - pre generator hooks for postgres to set languages etc. (patch in queue) - support for postgres inheritance mapping to class extends. - more support for High end databases.. - oracle etc. - better validation based on table type data. - probably run time querying of database for types.. Most of these are ideas that have been thrown at me from the many contributors of DB_DataObject. As far as I can see, (although I'll live to regret it.) - the current API is stable and I cant see any major deficiencies in it that mean that it would need breaking in the future.. (which is why it was switched to stable a few releases back..) Hope this gives you an idea of where it is.. Regards Alan Wolfram Kriesing wrote:

Martin Honermeyer wrote:

Hello, I am undetermined whether to use DB_QueryTool or DB_DataObject in my future projects. They are both very similar in function and features. Can anyone give me a hint of which one to prefer? The future development of those packages is also important to me. Does anybody know if those packages are going to be developed much further?

the main differences between those two are that DataObject maps a table onto an object, which means its columns onto properties. QueryTool simply supports you when building a query, it also handles joins to multiple tables. i would say compared to DataObject it focuses more on query building (is that right Alan?) since i am the maintainer of QueryTool i think i need to leave it up to you to decide :-) Just one thing you can be sure of is that QueryTool is maintained and developed