SDO not so disconnected

SDO for PHP is sold as a disconnected data graph. This would, imho, imply that switching between different sources for a SDO object should be peanuts. But it's not.

It is in fact just an extra layer/abstraction between a model and it's data source. Which gives it this advantage: a singe interface the model can use on the SDO. SDO is based on the Data Transfer Object design pattern. This pattern, also known as value object pattern(nl), is about transferring data, in an object, within an application.

I think the SDO technology can be enhanced by adding syncing/merging capabilities between two SDO's.
Something like an merge_data and/or sync SDO functionality.

To be honest, for a really disconnected data graph, you would use xml or other string representations of a data object. This is done with the SCA part of this technology with SOA/XML.

Another thing that is bothering me is that for a relational DAS, i need to inform the SDO about it's data model via associative arrays. Most databases have meta data capabilities, but PDO is lacking here.
Perhaps it is possible to "extend" schema (with our own namespace") to describe the model?
This, in combination with the active record pattern should provide us with a way of automating the creation of the models and schema's.

The good news is that converting dbase query output to xml is incredibly easy, i still need 2 das, but the xml version can be an empty document. All you would need to do is fill that document with the sdo content of it's root object and voila, 1 command later (save) and we have a xml string.

Funny news is that the code behind the relational DAS is PHP.

tags:
sdo