Open thismatters opened 5 years ago
I'll be damned if it didn't get me again! Found my own question!
@thismatters found some solution to this?
The solution I found was to not use the IntegerField
, I used the DecimalField
instead and set decimal_place=0
to make it behave like an integer.
Python 3.6.6 Django 2.0.6 django-cryptography 0.3
I can create encrypted IntegerFields just fine when using sqlite as my db backend, but when I switch to using PSQL I get the following when I runserver:
I get a similar error when I try database migrations:
This seems like a shortcoming of the postgres db backend, but I thought I would report it here in case there is anything that can be done about it.
Edit: using a
DecimalField
withdecimal_place=0
is a pretty suitable workaround.