Modify ↓
Ticket #87 (accepted defect)
migrating models from an abstract model class
| Reported by: | Antonius Common | Owned by: | andrew |
|---|---|---|---|
| Priority: | major | Milestone: | The Future |
| Component: | commands | Version: | |
| Keywords: | Cc: |
Description
Hi Fellows,
Commendations upon South, I LOVE IT.
However, I had no luck with adding a column to the base abstract model class, of which there are three slightly different inherited model classes.
Does it work?
Attachments
Change History
Note: See
TracTickets for help on using
tickets.

Nope, that won't work right now, but it probably should. It's a little more difficult than just saying "Add this to all subclasses", however. We'd have to make sure that none of the subclasses already had a field with that name, and if so, what should be the correct behavior.
Until we get this into South, you're obviously able to setup a migration that just adds the field to each model separately. Calling --add-field 3 times on the startmigration command, specifying each subclass name and field name should do the trick.