Hartym wrote: > ok i see your point, but.... > should we generate it differently depending on column type? > dodnt you think doctrine's power comes in great measures from the facts > that it does _not_ generate redundant code like propel? > anyway, i think that thoose ugly static methods in sfDoctrineRecord > should not stay there.
yes, well .. for this i am not sure if the different template approach is the right way to go. i guess what we really want is an AOP solution, but I dont quite see how to implement that in PHP. but having different base classes for this tiny feature seems overkill. it also makes it overly hard in case i want to add some other behavior to several classes. having to manually select the proper base class is even worse imho. regards, Lukas --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
