Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: Current Version
-
Fix Version/s: TAG 2016/17 Sprint 2
-
Component/s: OIOIOI
-
Labels:None
Description
And these choices actually depend on the set of configured apps. We should not serialize the choices and create database fields which do not limit the content of these fields.
I suppose we need a custom EnumField.
I suppose we need a custom EnumField.
https://gerrit.sio2project.mimuw.edu.pl/2672
SIO-1600Django 1.7 migrations serialize choices for EnumFieldsChange-Id: I363b0d323236f24ca10d8e778a614e6a3991c1d0