I have figured this one out, thankfully. In my schema.yml, I define two aliases:
session_db: -- tables propel: -- tables The schema.yml for sfGuardPlugin defines: propel: -- tables It seems that if I have session_db first in my schema.yml, the code generated in sfGuardPlugin is different than if I place it in the order where session_db: is defined after the propel: alias. Steve On Apr 7, 3:53 pm, Steve the Canuck <steve.san...@gmail.com> wrote: > Hi, > > I created a separate session database today to store my sessions. The > rest of my object model resides in a database with the alias "propel" > in databases.yml. When I created the session database and regenerated > my model, the sfGuardPlugin's model classes no longer seem to have > methods that provide access to other relationships in my model. In my > case, there is a method called getConsumers() that was previously on > my sfGuardPlugin OM class. > > Has anyone else come across this, and do you know how to fix it? > > Thanks, > Steve --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
