On 7/22/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote: > What is the current wisdom on OneToOne? Will it be finalized soon? Ever?
As I understand it from a conversation I had the other day, nothing whatsoever will happen until subclassing is straightened out. At that point we'll move to recommending people use subclassing for a lot of the things OneToOneField is currently used for, because in many cases that's the behavior people really want. OneToOneField itself will remain, and there will still be cases -- like extending User -- where it's the best solution, but the underlying behavior of the field type may change somewhat. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
