Absolutely - 'email' should be added to sf_guard_user schema - it doesn't need to be a required column though (to maintain backward compatibility), a caveat of using password reset functionality should be that email column has been changed to both unique/required.
Nicolas's implementation (in Symfonians) seems to be what I was thinking of, I'm going to be looking at it later today or early tomorrow. As an interim solution I like the idea of using AtlernativeSchemaPlugin so as not to 'break' the plugin, and to keep it future-proof. On 26 Mar 2008, at 15:50, Nicolas Perriault wrote: > > On Wed, Mar 26, 2008 at 3:47 PM, forkmantis <[EMAIL PROTECTED]> > wrote: > >> That being said, what I've done in my own projects is make my own >> myGuardPlugin in which I've added an sfGuardUserProfile, password >> recovery, and other features typical to my own projects. > > You can also use sfPropelAlternativeSchemaPlugin to add an 'email' > column to the existing sf_guard_user table: > http://trac.symfony-project.com/wiki/sfPropelAlternativeSchemaPlugin > > I agree that an 'email' column should exist by default in > sf_guard_user table, it's a so common needed information on web apps > nowadays. It'd be a bit overkill to manage a foreign profile table to > just store such a column... > > ++ > > -- > Nicolas Perriault > http://prendreuncafe.com/blog > GSM: 06.60.92.08.67 > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
