One correction: One 'child' class (ie. with a OneToOneField) does always keep the reference to the base class in it's pk column.
A couple of additions: - the OneToOneField is obviously partially working, as even when the reference is dnot there, the standard 'id' field name is correctly replaced with <parent_id>. - with MySQL, things work slightly differently. The child class that always works keeps the reference as in SQLLite. The other classes have an post-creation ALTER TABLE clause that explicitly adds in a (named) reference. Odd. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
