Developers looked down onto it from lofty heights, and ended up making rubbish. Over and over. Someone finally said, nuts to this, let's use postgres.
Uhm... shit, porting. Thus:
... were born. And useful. Patterns began to invade the scriptkiddy space, though they didn't know it. Porting was said to be easy, but no one really used it. They did, however, like being able to set up basic configuration and just make it work - clean looking code, ooh.
For me, it was ADODB and PEAR::DB that lead me onto the OOP circuit for PHP. I went off and learnt Java and you know, turned 17 and such. Going back, I saw how wonderful PEAR was in theory - I threw out everything else and started using PEAR::DB.
Alot.
It's been a beautiful relationship. But after endlessly and unconciously adopting poor attempts at a good ORM/DAO pattern, it began to falter.
Now it's time for the next step up. Take other people's proven patterns and run with them.
The only question for me is, which do I choose?
- PEAR::DB_DataObject - I have heard good things and bad things - rapid prototyping, but when you get to the advanced stuff...
- PHP 5.1's PDO - Untested API
- Screw it, just go over to RoR
- PECL::DBDO - C implementation of DB_DataObject [same lead] but very untested and unavailable largely.
1 comment:
After a bit of a play with DB_DataObject as a data exposure tool, I'm in love.
It's also given me a few ideas...
Post a Comment