> Not really. But from the question:
> "But how can I tell south to fill the super class with the data from the
> old schema?"
Well, in aswer to this, and Tom's remarks, you assumed he wanted to
have a new table because he was asking how to populate it, I assumed
he maybe doesn't know about abstract models because he said he's just
getting started programming (or at least on py/dj) and maybe he wasn't
sure what behavior he needed, and what were his options. I *do* start
saying "if you don't want Base instances".
and from Tom's:
> In the example, it is evident that the OP wants MTI, since he includes
> the foreign key links in the class definition - there is no clearer
> indicator than this!
The evidency of this gets flimsy, AFAICS, if you take in consideration
that he's refactoring code, and having two separate tables was good
enough for him until he "got a little better with python and django".
So, yes, this goes down, I think, if at any point he has a view where
he joins both groups of objects.
> And you're spreading records over two different tables and making it
> impossible to enforce uniqueness on shared attributes. So it's not just
> about creating an instance.
tru dat..
And yeah, the holy war wouldn't be on inheritance types, but rather on
reading comprehension, it seems ;)
--
"The whole of Japan is pure invention. There is no such country, there
are no such people" --Oscar Wilde
|_|0|_|
|_|_|0|
|0|0|0|
(\__/)
(='.'=)This is Bunny. Copy and paste bunny
(")_(") to help him gain world domination.
--
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
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
