重用Django模型

Question

I have an app with a bunch of models and templates to perform a certain task (it's called a "user access review", but that's not important - the app is called "uar"). When the users have completed their task, we want to archive the data from the main models into what we're calling "history" tables. Those tables are identical in structure to the original "uar" tables, but may live in another database or may be in the same database. They will, however, be read-only except by the process that archives them into these history tables, and possibly a task that expires items after a certain number of years.

Since I wanted the exact same model structure but different names, I thought I'd just make an app called "uar_history" and symlink the models.py file between the two apps. But when I attempt to syncdb the new models, I get a lot of complaints about the models not validating because of the related_name back link on the foreign keys.

Is there a better approach to this? Should I just make all my archive tables sub-classes of the model classes instead?

Answer 1

@Brandon gave the right answer, you should use a common abstract model for the shared definition. They can be in the same file or separate model files (I chose common , current , and history as the apps for this example):

common/models.py

class CommonPostModel(models.Model):
    title = models.CharField(max_length=255)
    body = models.TextField()

    class Meta:
        abstract = True

current/models.py

class CurrentPostModel(CommonPostModel):
    pass

history/models.py

class ArchivePostModel(CommonPostModel):
    pass