Changes between Version 1 and Version 2 of Ticket #29790


Ignore:
Timestamp:
Oct 1, 2018, 12:17:34 PM (6 years ago)
Author:
Richard Ebeling
Comment:

This commit changed the behavior: 02365d3f38a64a5c2f3e932f23925a381d5bb151

As a sample project I can link the project we are currently working on, ​https://github.com/fsr-itse/EvaP/tree/release. A simple ./manage.py reset_db --noinput && ./manage.py migrate will trigger the error. Is this what you wanted?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #29790 – Description

    v1 v2  
    99{{{django.db.utils.ProgrammingError: multiple primary keys for table "evaluation_textanswer" are not allowed}}}
    1010
     11This commit changed the behavior: 02365d3f38a64a5c2f3e932f23925a381d5bb151
     12
    1113It works if we add a RemoveField instruction for the old id before setting {{{primary_key=True}}} on the new UUIDField. But this will trigger the SQLite bug listed above. Changing the old AutoField to {{{primary_key=False}}} where the RemoveField instruction would be doesn't fix the error.
    1214
Back to Top