Closed synic closed 8 years ago
I can't tell what's going on from that snippet. You're filtering on number
- is that defined in TimestampMixin
, or was that just a typo, did you mean from_number
?
Sorry, yeah, it's from_number.
Any updates on this one? We haven't started using pgcrypto because of this error.
I can't reproduce this. The unit tests (which use Django 1.7, and pass on Python 2 and 3) already include an exact lookup on an EncryptedCharField:
https://github.com/dcwatson/django-pgcrypto/blob/master/tests/core/tests.py#L61
Do you think you could put together a failing test case?
I will see if I can come up with something. Thank you
On Thu, Mar 5, 2015 at 1:26 PM, Dan Watson notifications@github.com wrote:
I can't reproduce this. The unit tests (which use Django 1.7, and pass on Python 2 and 3) already include an exact lookup on an EncryptedCharField:
https://github.com/dcwatson/django-pgcrypto/blob/master/tests/core/tests.py#L61
Do you think you could put together a failing test case?
— Reply to this email directly or view it on GitHub https://github.com/dcwatson/django-pgcrypto/issues/12#issuecomment-77444496 .
Re-open with a test case if you can reproduce.
In my case, I am getting this issue when the field has empty values than the filter not working for that field, and getting this issue, I was filtering an EncryptedCharField with 700 rows and one-row was with an empty string.
And the error: