Although that's probably technically correct, it's a REALLY bad code smell. It breaks the DRY principal.
Surely, you want to create a single model, and have a single column that differentiates (Column Aggregation) whether the record is an employee or candidate? Or, alternatively, create a base class and extend from this (Concrete Inheritance) for employee and candidate respectively? Take a look here for more info : http://www.doctrine-project.com/documentation/manual/1_0/en/inheritance On 11 Feb 2009, at 09:10, Bernhard Schussek wrote: > > You just need to create two modules with the same model. > > $ php symfony propel:generate-admin app Model --module="firstmodule" > $ php symfony propel:generate-admin app Model --module="secondmodule" > > > Bernhard > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
