Propel also has behaviours -- you just have to enable it when you build the model.
What I find annoying is that whilst methods such as doDelete have multiple extension points with behaviours the get/set functions have no override points. This means that common code can't be added without editing the classes -- or providing a custom generator class. (I have a versioning mechanism that isn't restricted to a single table and also has 'states' -- individual objects may or may not be versioned/ require approval for changes. Each class has to override the setter for the [common] fields which makes this happen in order to access the common code. The delete aspect can be done using the built in behaviour hooks) Alistair On Mar 25, 2009 1:48 AM, "Campezzi" <[email protected]> wrote: Hello everyone, Thanks for the replies. From what I heard, I'd better take a closer look into Doctrine before "sealing the deal" with Propel. At the moment, I'm inclined to think that working with Propel is a bit more intuitive (at least it has been easier for me to understand), but I have already run into some JOIN quirks. Also, the Behaviors in Doctrine seem to be especially useful for the project I'm starting now, which will only use soft deletes - to accomplish that in Propel, I was overriding the doSelect and doDelete methods in every peer class - quite a bit of work! Kind Regards, Campezzi On Mar 24, 9:58 am, Campezzi <[email protected]> wrote: > Hello there, > > I've been a PHP devel... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
