We should really sit down together and talk about the possibilities MDB
could add to DB_DataObjects. I have not yet used the tool, but it seems
it's quite a hit. If we were to combine the datatype abstraction with
DB_Dataobjects plus XML Schema Management things will get all the more
interesting.
+1 :) - I guess it's more a mater of time and motivation. - if somebody submits a patch to change dataObjects to work with mdb .. - I'd be very happy.
Regards
Alan
Well, I had tried to do it some time ago, but it was not that easy...
IMO it would be easier to rewrite the whole thing from the ground up,
already with "containers" (DB, MDB, XML, LDAP...) in mind.
I tried to do such a thing with QueryTool, but a "container" schema
would need too many "redirected" methods, since this tools are supposed
to work directly with databases, and not only using them for storage purposes
like in PEAR::Cache or Mail_Queue.
I hope a simple example will be clearer:
==============================================
myBaseClass
{
var $container; // db container. May be a DB or MDB object
// my common methods
function getAll()
{
// all methods should point to the container's specific ones:
return $this->container->getAll();
}
}
myBaseClass_Container
{
// abstract class
}
class myBaseClass_Container_mdb extends myBaseClass_Container
{
//...
function getAll()
{
//...
}
}
==============================================
See what I mean? Of course this is just one way to do it, but PHP4
can't (the way I see it) handle this situation in a more elegant way,
while it would be easier in a language like Java (or PHP5?).
If you have other suggestions or design ideas, please share them,
because I'm very interested too...
Regards,
Lorenzo