It really depends on how your models are related. It's not really clear exactly what it is that you are trying to do.
Essentially, you attach the logic to an event (eg preInsert) - so you could (for instance) clone your object at that point, change some properties, and commit both. I used a Doctrine_Record_Listener to keep user account details synchronised in 2 different databases, with different schemas (1 way only), and used sfGuard's external authentication facility to authenticate against the 'foreign' database. On 5 Mar 2009, at 21:45, Daniele wrote: > > Thanks for reply Lee. > Yes, I'm using Doctrine! > I have taken a look in the documentation at Record Listeners, but I do > not understand how listener architecture can help me. > Can you give me some additional indication? > > > On Mar 5, 5:28 pm, Lee Bolding <[email protected]> wrote: >> If you're using Doctrine, you can use a Doctrine_Record_Listener (or >> similar) >> >> On 5 Mar 2009, at 16:00, Daniele wrote: >> >>> Hi all, >> >>> I cannot really understand what is, in Symfony 1.2, the way to >>> make a >>> module with forms to create or to update multiple instances of a >>> model >>> at a time. >> >>> It is possible to start by the class of model's form or is necessary >>> to create a completely new form class? >> >>> Someone know the correct way to start? >> >>> thanks in advance! > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
