> > anyway I think refactoring propel into a php extension is the futureproof
> > solution.
> this sounds like something that might work. what about actually
> extending PDO for this?
> Whilst we are at it, how about a mapping configuration so you don't
> have to touch the classes/objects you want to persist in the db?
I never do, in fact any object I generate (like Document.php DocumentPeer.php)
which you're supposedly cool to edit. I leave be... I want a fully abstracted model.
so Im never going to make it impure by putting regular hand typed code into it...
I think the whole point is to automate the M.. the model layer.. the layer in which
any bug is likely to cause data corruption. So XML -> Data Objects and that's it.
This is why I think propel lends itself to web frameworks because the separated
controller is a good place to wire these generated db objects together, simply
set foreign dependency with the </foreign tag and the save and validate inherits the
proper methods to deal with an abstraction of the database table. keep the table
names not pluralized, lower cased with underscores and you're well abstracted.
> I like a domain model that isn't fully aware of all the dependencies to
> whatever persistence engine is used.
and with that, that's exactly what you'll get.
> AOP maybe? Ups another 'buzzword' :-)
not really...not anymore than OCaml ;)