SmileyChris wrote:
> According to the docs:
>
> "The semantics of one-to-one relationships will be changing soon, so we
> don't recommend you use them. If that doesn't scare you away, keep
> reading."
>
> It scares me a bit. Can anyone expand on the "changing semantics" or
> point me to an existin
This works perfectly well for me
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
"James Bennett" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On 5/12/06, Andrew Badstubner <[EMAIL PROTECTED]> wrote:
> > I need to use this, and would love some more information.
> From what I understand, one-to-one relationships will be obsoleted by
> proper subclassing of mo
On 5/12/06, Andrew Badstubner <[EMAIL PROTECTED]> wrote:
> I need to use this, and would love some more information.
Fromwhat I understand, one-to-one relationships will be obsoleted by
proper subclassing of models; rather than tying a new model to an old
one, you'll just subclass the old.
--
"
> "The semantics of one-to-one relationships will be changing soon, so we
> don't recommend you use them. If that doesn't scare you away, keep
> reading."
>
> It scares me a bit. Can anyone expand on the "changing semantics" or
> point me to an existing discussion?
+1
I need to use this, and woul
I'd love to know more too and can't find anything relevant in the
developer's group.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegrou
According to the docs:
"The semantics of one-to-one relationships will be changing soon, so we
don't recommend you use them. If that doesn't scare you away, keep
reading."
It scares me a bit. Can anyone expand on the "changing semantics" or
point me to an existing discussion?
Thanks
--~--~---
7 matches
Mail list logo