Uniform content type tables with multiple databases

[Mario Taddei]

Hi all, 

I noticed that with multiple databases, the content_type tables are not filled in the same way. It is not a bug, but having uniform content type tables through multiple databases makes life easier.

If 'django.contrib.contenttypes' app comes before 'django.contrib.auth' in INSTALLED_APPS
the content_type table is filled here: https://github.com/django/django/blob/1.8.9/django/contrib/contenttypes/management.py#L53 

else (only in the database where 'auth' is migrated, previous method for the other databases)
it is filled by the method get_for_model() https://github.com/django/django/blob/1.8.9/django/contrib/contenttypes/models.py#L69
called in the 'django.contrib.auth' signal handler: https://github.com/django/django/blob/1.8.9/django/contrib/auth/management/__init__.py#L82

For the moment I adopted this solution (don't know if it is the best): 
'contenttypes' before 'auth' in INSTALLED_APPS
and this little modif using sorted() method: https://github.com/mariuccio/django/blob/stable/1.8.x/django/contrib/contenttypes/management.py#L50


Thanks for any advice,

Mario

[Tim Graham]

I'm not sure if anything could or should be done, but I noticed a warning in the documentation that Aymeric added:

"If you’re synchronizing content types to more than one database, be aware that their primary keys may not match across databases. This may result in data corruption or data loss."

https://github.com/django/django/commit/a026e480d