On 5/1/06, medhat <[EMAIL PROTECTED]> wrote: > > > [EMAIL PROTECTED] wrote: > > Joseph Kocherhans wrote: > > > The current trunk and magic-removal docs say this about OneToOneField: > > > > [snip] > > > > No feedback, so I've commited a patch. OneToOneField now behaves like > > ForeignKey for adding objects in the admin system, and is displayed as > > a read only field for the change form. Here's the ticket again. > > > > http://code.djangoproject.com/ticket/1681 > > > > Joseph > > Wouldn't moving this to the base class also affect ManyToManyField?
Yep, it would. Good catch. \ME smacks head for trying to avoid copy/pasting a method at the last minute. Fixed in [2802] Joseph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
