Migrating Built-in Django Models When Upgrading

We're using an older version of Django (1.1.1) and are preparing to upgrade to the latest version (currently 1.2) soon.

None of my searches have brought up the topic of migrating database tables (auth_user, etc.) across Django versions. Using syncdb only works for creating new tables but has no effect on existing tables.

I'm under the impression that the upgrade is not simply linking to a new versio开发者_Go百科n of the Django files but that we also need to manage the migration of our database since we rely on some built-in Django apps (django.contrib.auth, django.contrib.sites, etc.). We're planning to use South to manage the database migration.

Is this something handled internally by Django? Am I trying to solve a problem that doesn't exist?

---

There are no changes to the django.contrib.auth or django.contrib.sites models between 1.1.1 and 1.2.5 so you won't need to do any database migration.