Hmm... Well i cant say that i see a use case for many owners. IMO, either an entity owns it or it doesnt. I think having many owners would be a special case handled by the developer utilizing it. But thats just my 2¢.
Perhaps i too quickly adopt *nix permissions/ACLS as my default model for ownership and permissions? :-) Florian wrote: > > Someone told me exactly the same remark yesterday. > The first version has used a custom column ( I changed the model to > handle many2many ). > > The only thing I could answer is that you can handle many owners on > the same object ( as ActAsTaggableBehavior do with sf_tag and > sf_tagging ). > > Maybe should I permit to use both a many2many relationship and a > custom column ? > > > > On 1 fév, 21:03, Ant Cunningham <[email protected]> wrote: >> My only question/criticism is why have schema/table? >> >> Why not store the owner_id directly on the owned model and then require >> the user to configure the column? this is similar to how the other ActAs >> behavaiors work. >> >> Florian wrote: >>> Hello community, >>> I would like to have your opinion on this plugin : >>> http://code.google.com/p/sfownedbehavior/source/browse/trunk/lib/sfPr... >>> I think this fonctionnality is not yet handled by any other plugin, so >>> it would be great if this plugin can be helpfull ! >>> Regards, >>> Florian. >> > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
