What is the best approach to change primary keys in an existing Django app?

by

Agreed, your model is probably wrong.

The formal primary key should always be a surrogate key. Never anything else. [Strong words. Been database designer since the 1980’s. Important lessoned learned is this: everything is changeable, even when the users swear on their mothers’ graves that the value cannot be changed is is truly a natural key that can be taken as primary. It isn’t primary. Only surrogates can be primary.]

You’re doing open-heart surgery. Don’t mess with schema migration. You’re replacing the schema.

  1. Unload your data into JSON files. Use Django’s own internal django-admin.py tools for this. You should create one unload file for each that will be changing and each table that depends on a key which is being created. Separate files make this slightly easier to do.

  2. Drop the tables which you are going to change from the old schema.

    Tables which depend on these tables will have their FK’s changed; you can either
    update the rows in place or — it might be simpler — to delete and reinsert
    these rows, also.

  3. Create the new schema. This will only create the tables which are changing.

  4. Write scripts to read and reload the data with the new keys. These are short and very similar. Each script will use json.load() to read objects from the source file; you will then create your schema objects from the JSON tuple-line objects that were built for you. You can then insert them into the database.

    You have two cases.

    • Tables with PK’s change changed will be inserted and will get new PK’s. These must be “cascaded” to other tables to assure that the other table’s FK’s get changed also.

    • Tables with FK’s that change will have to locate the row in the foreign table and update their FK reference.

Alternative.

  1. Rename all your old tables.

  2. Create the entire new schema.

  3. Write SQL to migrate all the data from old schema to new schema. This will have to cleverly reassign keys as it goes.

  4. Drop the renamed old tables.

 

More Related Contents:

  1. Loading initial data with Django 1.7 and data migrations
  2. Django – How to rename a model field using South?
  3. -bash: ./manage.py: Permission denied
  4. Easiest way to rename a model using Django/South?
  5. What is your favorite solution for managing database migrations in django? [closed]
  6. Pillow installed, but getting “no module named pillow”
  7. How to query as GROUP BY in django?
  8. Does Django scale? [closed]
  9. In Django, how does one filter a QuerySet with dynamic field lookups?
  10. Django equivalent for count and group by
  11. How to redirect with post data (Django)
  12. Django/Python Beginner: Error when executing python manage.py syncdb – psycopg2 not found
  13. Django REST Framework POST nested objects
  14. django-filter use paginations
  15. Is this the way to validate Django model fields?
  16. Django: signal when user logs in?
  17. Django: Get an object form the DB, or ‘None’ if nothing matches
  18. “no such table” exception
  19. Proper way to consume data from RESTFUL API in django
  20. How do I convert kilometres to degrees in Geodjango/GEOS?
  21. Django Celery Logging Best Practice
  22. Django: using and POST
  23. Django filter JSONField list of dicts
  24. how to manually assign imagefield in Django
  25. How to add custom field in ModelSerializer?
  26. Run manage.py from AWS EB Linux instance
  27. How to perform filtering with a Django JSONField?
  28. “{% extends %}” vs “{% include %}” in Django Templates
  29. XlsxWriter object save as http response to create download in Django
  30. Apache mod_wsgi error: Forbidden You don’t have permission to access / on this server

Leave a Comment