UUIDfield based primary key error

[arzuhuseyn]

With UUID based primary key I get an error. Please, consider adding UUIDfield support.

[Andrew-Chen-Wang]

You can use migration modules in Django to store your new migrations. I don't think you'll break compatibility any time soon with SimpleJWT, so go at it: https://docs.djangoproject.com/en/dev/ref/settings/#migration-modules

You can visit cookiecutter-django to see how we do it with django.contrib.sites app

On the other hand, a different solution is that you'd need to make your own blacklist app since our migrations should not be touched in your virtualenv:

djangorestframework-simplejwt/rest_framework_simplejwt/token_blacklist/migrations/0010_fix_migrate_to_bigautofield.py

Lines 10 to 27 in ff59830

	class Migration(migrations.Migration):
	dependencies = [
	('token_blacklist', '0008_migrate_to_bigautofield'),
	]
	operations = [
	migrations.AlterField(
	model_name='blacklistedtoken',
	name='id',
	field=models.BigAutoField(primary_key=True, serialize=False),
	),
	migrations.AlterField(
	model_name='outstandingtoken',
	name='id',
	field=models.BigAutoField(primary_key=True, serialize=False),
	),
	]

BTW, you can't cast integers to a UUID. First convert it to a string then to a uuid using raw sql. Someone's prob already done it for you online.

---

However, assuming you have UUIDField as your default primary key field for all Django apps in your project, most Django apps have BigAutoField as their defaults as well, but you most likely are trying to change the models via virtualenv which is not recommended at all. Unless you have sharded your project quite extensively already, I suggest you stick to BigAutoField until you have to change all your Django projects' installed third party apps to UUIDField.

But if you want to give it a go, then yea use migration modules.