Thanks All.
Thanks Javier.
That makes sense, I'm implementing it via a OneToOe relationship now.
On Sep 17, 4:38 am, Tom Evans wrote:
> On Wed, 2009-09-16 at 17:15 -0500, Javier Guerra wrote:
> > On Wed, Sep 16, 2009 at 1:01 PM, PlanetUnknown
> > wrote:
>
> > > Thanks Karen.
> > > Let me exp
> > wrote:
>
> > > Thanks Karen.
> > > Let me explain it a bit more.
> > > e.g.
> > > All CONTACT details are present in one table - email, home address,
> > > work address, home phone, work phone etc.
> > > Forget about the statement about growing for now.
> > > Since each user "has-a" contact i
On Wed, 2009-09-16 at 17:15 -0500, Javier Guerra wrote:
> On Wed, Sep 16, 2009 at 1:01 PM, PlanetUnknown
> wrote:
> >
> > Thanks Karen.
> > Let me explain it a bit more.
> > e.g.
> > All CONTACT details are present in one table - email, home address,
> > work address, home phone, work phone etc.
On Wed, Sep 16, 2009 at 3:15 PM, Javier Guerra wrote:
>
> On Wed, Sep 16, 2009 at 1:01 PM, PlanetUnknown
> wrote:
>>
>> Thanks Karen.
>> Let me explain it a bit more.
>> e.g.
>> All CONTACT details are present in one table - email, home address,
>> work address, home phone, work phone etc.
>> Fo
On Wed, Sep 16, 2009 at 1:01 PM, PlanetUnknown
wrote:
>
> Thanks Karen.
> Let me explain it a bit more.
> e.g.
> All CONTACT details are present in one table - email, home address,
> work address, home phone, work phone etc.
> Forget about the statement about growing for now.
> Since each user "h
On Wed, Sep 16, 2009 at 2:01 PM, PlanetUnknown wrote:
>
> Thanks Karen.
> Let me explain it a bit more.
> e.g.
> All CONTACT details are present in one table - email, home address,
> work address, home phone, work phone etc.
> Forget about the statement about growing for now.
> Since each user "ha
Thanks Karen.
Let me explain it a bit more.
e.g.
All CONTACT details are present in one table - email, home address,
work address, home phone, work phone etc.
Forget about the statement about growing for now.
Since each user "has-a" contact it is a pure one-to-one relationship
and not a one-to-man
On Wed, Sep 16, 2009 at 10:15 AM, PlanetUnknown
wrote:
>
> For example - User HAS "Contacts"; User HAS "Preferences"
> Usually (I'm from an Oracle/Java background) the Contacts table would
> have a "user-id" foreign key.
> However Django models refer Foreign Key relations as "Many-to-one",
> but t
The OneToOne relationship seems to be more of an inheritance type of
relationship, hence that cannot be used.
On Sep 16, 10:28 am, Craig McClanahan wrote:
> On Wed, Sep 16, 2009 at 7:15 AM, PlanetUnknown
>
> wrote:
>
> > For example - User HAS "Contacts"; User HAS "Preferences"
> > Usually (I'm
On Wed, Sep 16, 2009 at 7:15 AM, PlanetUnknown
wrote:
>
> For example - User HAS "Contacts"; User HAS "Preferences"
> Usually (I'm from an Oracle/Java background) the Contacts table would
> have a "user-id" foreign key.
> However Django models refer Foreign Key relations as "Many-to-one",
> but t
For example - User HAS "Contacts"; User HAS "Preferences"
Usually (I'm from an Oracle/Java background) the Contacts table would
have a "user-id" foreign key.
However Django models refer Foreign Key relations as "Many-to-one",
but that is not true in my case.
There is only one Contact table for a U
11 matches
Mail list logo
