James Bennett wrote: > On 5/30/06, Russell Blau <[EMAIL PROTECTED]> wrote: >> "it'll work for now..." BUT, as has been discussed here over the past few >> weeks, it is not guaranteed to work for the future -- there is a warning in >> the new docs *not* to use OneToOneField because it's expected to change >> soon. > > That warning, I believe, has to do with plans to deprecate one-to-one > relations once model subclassing works. One-to-one relationships > between models are basically a really verbose type of subclassing. >
imho one-to-one "subclassing" is just one of the possibilities as discussed at http://code.djangoproject.com/wiki/ModelInheritance. for example, my situation: i have a lot of models, and there are some fields that have to be there for every model: creation_date, who_created_it, score, whatever. and i hate to cut&paste it into every model. so i'd prefer to do it with inheritance. but i do not want to spend a join everytime i look up the creation_date. i would rather have it collapsed into one table. probably the question is: do you expect to use instances of the parent class? if yes, then probably the join-approach is better, if not, then probably the collapse-into-one-table approach is more suitable. gabor --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
