On Wednesday 05 April 2006 21:35, Rudolph wrote: > Is that an inconsistancy to be removed (ie a bug)?
No, it's intended behaviour. The _set stuff is only there because for the 'other' end of these relationships it is possible that there is no name defined, so there needs to be a way of coming up with name automatically. The way it is at present allows you to write stuff like myobject.children.filter(..etc), rather than myobject.child_set Luke -- "Despair: It's always darkest just before it goes pitch black." (despair.com) Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users -~----------~----~----~----~------~----~------~--~---
