On 12/14/06, Crispin Bennett <[EMAIL PROTECTED]> wrote: > I assume it would be possible to get at child instances via some kind > of introspection on instances of the base class (ie. so I could > iterate usefully over collections of base class instances)?
You may want to read this thread from the developers list, which goes through some of how this will work (and contains references to earlier threads discussing the full API): http://groups.google.com/group/django-developers/browse_thread/thread/7d40ad373ebfa912/ > I'll look into how to do such a thing, but, being new to both python > and django, would like to know first if such a thing is feasible. Not at the moment. Representing class hierarchies robustly and efficiently in a relational database (which isn't designed for hierarchical relations) is tricky at best, which I think is one of the reasons behind the delay in getting it working "properly". Your best bet right now is a one-to-one relationship, which exposes an API not dissimilar from the one Malcolm has described -- querying against a particular model class only returns instances of that model class, but fields from parent or child classes will be accessible if you explicitly ask for them from a particular instance (for example, if you have a class Thing and a class Animal related to it, each Animal will have a 'thing' attribute which will query the fields of the related Thing object). -- "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 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?hl=en -~----------~----~----~----~------~----~------~--~---
