Thanks..
On Oct 9, 1:32 pm, Gábor Fási wrote:
> http://www.doctrine-project.org/documentation/manual/1_1/en/inheritan...
>
> On Fri, Oct 9, 2009 at 12:04, tirengarfio wrote:
>
> > What do you mean with "Doctrine "simple inheritance""??
>
> > On Oct 8, 9:50 pm, Tom Boutell wrote:
> >> You'd hav
http://www.doctrine-project.org/documentation/manual/1_1/en/inheritance#simple
On Fri, Oct 9, 2009 at 12:04, tirengarfio wrote:
>
> What do you mean with "Doctrine "simple inheritance""??
>
>
> On Oct 8, 9:50 pm, Tom Boutell wrote:
>> You'd have to change the schema.yml of the plugin.
>>
>> But
What do you mean with "Doctrine "simple inheritance""??
On Oct 8, 9:50 pm, Tom Boutell 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
I'm curious what you regard as the advantage? Avoiding certain JOINs?
On Oct 8, 9:32 am, tirengarfio 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.
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 s
