well, I am implementing a multiple db feature on an exist django project. After I create and setup the secondary db to django, the first thing I did is running syncdb and migrate, which will create a lot built-in django tables, includes django_content_type table.
Then I realize, the records in the new django_content_type table are different from the one in primary db. To be more specific, the primary key is different.
Let's say I have a record in primary db django_content_type table looks like following:
id | name | app_label | model
----+------+-----------+-------
33 | Tag | taggit | tag
However, after syncdb and running migrations, I got following in my secondary db:
id | name | app_label | model
----+------+-----------+-------
11 | Tag | entities | tag
I kind of hate to have two inconsistent django_content_type sitting in my two db. I tried to truncate one of them and load a fixture from another and failed, since django_content_type table is referred by most of other tables.
What is best way to handle things like this? I try to convince myself this won't matter, but I am afraid inconsistency will bite me in the future, so I really want to solve this issue.
Thanks in advance.