[symfony-users] Re: sfDoctrineGuardPlugin: anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile?
What do you mean with Doctrine simple inheritance?? On Oct 8, 9:50 pm, Tom Boutell t...@punkave.com wrote: You'd have to change the schema.yml of the plugin. But instead of doing that, you can use Doctrine simple inheritance to add the fields to that table. Simple inheritance is a lot less of a pain than using profiles and I recommend it. it's a shame that the sfDoctrineGuardPlugin manual doesn't steer users in that direction instead of just reiterating the Symfony 1.0/Propel style recommendation to use a separate profile table. On Oct 8, 9:32 am, tirengarfio tirengar...@gmail.com wrote: Hi, I have read an article (link below) about adding profiles to the users that are generated after building the sfDoctrineGuardPlugin models that are defined in its schema.yml. http://www.symfony-project.org/blog/2008/11/12/call-the-expert-custom... It says that if you want to add a profile to the users you should add a new model in schema.yml called for example Profile and that must be related to sfGuardUser model. My question: Is there anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile? Ciao Javi --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[symfony-users] Re: sfDoctrineGuardPlugin: anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile?
http://www.doctrine-project.org/documentation/manual/1_1/en/inheritance#simple On Fri, Oct 9, 2009 at 12:04, tirengarfio tirengar...@gmail.com wrote: What do you mean with Doctrine simple inheritance?? On Oct 8, 9:50 pm, Tom Boutell t...@punkave.com wrote: You'd have to change the schema.yml of the plugin. But instead of doing that, you can use Doctrine simple inheritance to add the fields to that table. Simple inheritance is a lot less of a pain than using profiles and I recommend it. it's a shame that the sfDoctrineGuardPlugin manual doesn't steer users in that direction instead of just reiterating the Symfony 1.0/Propel style recommendation to use a separate profile table. On Oct 8, 9:32 am, tirengarfio tirengar...@gmail.com wrote: Hi, I have read an article (link below) about adding profiles to the users that are generated after building the sfDoctrineGuardPlugin models that are defined in its schema.yml. http://www.symfony-project.org/blog/2008/11/12/call-the-expert-custom... It says that if you want to add a profile to the users you should add a new model in schema.yml called for example Profile and that must be related to sfGuardUser model. My question: Is there anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile? Ciao Javi --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[symfony-users] Re: sfDoctrineGuardPlugin: anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile?
Thanks.. On Oct 9, 1:32 pm, Gábor Fási maerl...@gmail.com wrote: http://www.doctrine-project.org/documentation/manual/1_1/en/inheritan... On Fri, Oct 9, 2009 at 12:04, tirengarfio tirengar...@gmail.com wrote: What do you mean with Doctrine simple inheritance?? On Oct 8, 9:50 pm, Tom Boutell t...@punkave.com wrote: You'd have to change the schema.yml of the plugin. But instead of doing that, you can use Doctrine simple inheritance to add the fields to that table. Simple inheritance is a lot less of a pain than using profiles and I recommend it. it's a shame that the sfDoctrineGuardPlugin manual doesn't steer users in that direction instead of just reiterating the Symfony 1.0/Propel style recommendation to use a separate profile table. On Oct 8, 9:32 am, tirengarfio tirengar...@gmail.com wrote: Hi, I have read an article (link below) about adding profiles to the users that are generated after building the sfDoctrineGuardPlugin models that are defined in its schema.yml. http://www.symfony-project.org/blog/2008/11/12/call-the-expert-custom... It says that if you want to add a profile to the users you should add a new model in schema.yml called for example Profile and that must be related to sfGuardUser model. My question: Is there anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile? Ciao Javi --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[symfony-users] Re: sfDoctrineGuardPlugin: anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile?
You'd have to change the schema.yml of the plugin. But instead of doing that, you can use Doctrine simple inheritance to add the fields to that table. Simple inheritance is a lot less of a pain than using profiles and I recommend it. it's a shame that the sfDoctrineGuardPlugin manual doesn't steer users in that direction instead of just reiterating the Symfony 1.0/Propel style recommendation to use a separate profile table. On Oct 8, 9:32 am, tirengarfio tirengar...@gmail.com wrote: Hi, I have read an article (link below) about adding profiles to the users that are generated after building the sfDoctrineGuardPlugin models that are defined in its schema.yml. http://www.symfony-project.org/blog/2008/11/12/call-the-expert-custom... It says that if you want to add a profile to the users you should add a new model in schema.yml called for example Profile and that must be related to sfGuardUser model. My question: Is there anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile? Ciao Javi --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[symfony-users] Re: sfDoctrineGuardPlugin: anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile?
I'm curious what you regard as the advantage? Avoiding certain JOINs? On Oct 8, 9:32 am, tirengarfio tirengar...@gmail.com wrote: Hi, I have read an article (link below) about adding profiles to the users that are generated after building the sfDoctrineGuardPlugin models that are defined in its schema.yml. http://www.symfony-project.org/blog/2008/11/12/call-the-expert-custom... It says that if you want to add a profile to the users you should add a new model in schema.yml called for example Profile and that must be related to sfGuardUser model. My question: Is there anything that advise against adding the profile fields in the sfGuardUser directly instead of define the model Profile? Ciao Javi --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
