Service Data Objects for PHP
Posted: Wed Aug 10, 2005 6:51 pm
Hi ppl
Came across this article describing SDO Objects for PHP:
http://www-128.ibm.com/developerworks/o ... w06PHP-SDO
EDIT: Mcgruff is still busy fixing the tag problem, so here is the url without tags:
http://www-128.ibm.com/developerworks/o ... w06PHP-SDO
My question is, does this really give a php coder an upper edge on the design of an application?
I have a pretty jacked "sql on the fly" sort of class, I automatically pick up the table schema, as they call it, and only update the fields to be updated etc. And keep the data persistent as they do anyway, using the session.
So I don't see the point in using SDO at all, it is like using a Templating engine. In my opinion, php is the Templating engine, so why re-invent the wheel?
Your feedback would be much appreciated. Inclined to the advantages of SDO over what Php already has to offer.
Came across this article describing SDO Objects for PHP:
http://www-128.ibm.com/developerworks/o ... w06PHP-SDO
EDIT: Mcgruff is still busy fixing the tag problem, so here is the url without tags:
http://www-128.ibm.com/developerworks/o ... w06PHP-SDO
My question is, does this really give a php coder an upper edge on the design of an application?
I have a pretty jacked "sql on the fly" sort of class, I automatically pick up the table schema, as they call it, and only update the fields to be updated etc. And keep the data persistent as they do anyway, using the session.
So I don't see the point in using SDO at all, it is like using a Templating engine. In my opinion, php is the Templating engine, so why re-invent the wheel?
Your feedback would be much appreciated. Inclined to the advantages of SDO over what Php already has to offer.