On Thu, 2007-10-11 at 06:47 -0700, Tai Lee wrote: > ForeignKey with unique=True does work and is the same at the SQL > level, but OneToOneField does have a couple of niceties attached to it > like adding the related object as an attribute to the model containing > the OneToOneField. If those could be re-added to ForeignKey fields > with unique=True, that would be a good start ;)
That sort of thing is one of the reasons I'm not actively agitating for OneToOneField to disappear at the Python level. It does have its uses. I was trying to stem the recent tide of comments in a few places that there is some great difference between 1-1 and 1-n with a unique constraint. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
