What I've done here is to remove the mapping from original to actual low level length.
Current status:
All fields mapped to text type field so no database validation is required against max length.
As I can see in django.db.model.fields.Field, themax_length only used as validator which result in comparing users value against the encrypted new size which is incorrect.
Solution:
I just removed the max_length so all comparison now happening actual max_length against users actual value which is the correct behavior as I see it.
@danaspiegel @waseem-omar Can you guys review this and let me know what do you think?
What I've done here is to remove the mapping from original to actual low level length. Current status:
text
type field so no database validation is required against max length.django.db.model.fields.Field
, themax_length
only used as validator which result in comparing users value against the encrypted new size which is incorrect.Solution:
I just removed the
max_length
so all comparison now happening actualmax_length
against users actual value which is the correct behavior as I see it.@danaspiegel @waseem-omar Can you guys review this and let me know what do you think?