| 17 | | Still, in the release notes for django 2.1 it should be noted that django's behavior was changed here. Also, I would appreciate if there was some kind of documentation on how you should migrate primary keys from a field to another if no two primary keys are allowed in between. There should be a way without squashing the migrations as we want to keep the history. |
| | 17 | Still, in the release notes for django 2.1 it should be noted that django's behavior was changed here. Also, I would appreciate if there was some kind of documentation on how you should migrate primary keys from a field to another if no two primary keys are allowed in between. There should be a way without squashing the migrations as we want to keep the history. |
| | 18 | |
| | 19 | We are running postgres version 9.6.9 and psycopg2-binary version 2.7.5. |
| | 20 | The migration error will not occur when using a SQLite database. |