We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encrypted fields are encrypted and then converted to base64 as noted here: https://github.com/kvesteri/sqlalchemy-utils/blob/master/sqlalchemy_utils/types/encrypted/encrypted_type.py#L114
We don't take into account the length of the additions from the cipher or base64 encoding. We should do that, and then update the strings and do a data migration to nuke a known case with schedule's detail field: https://thunderbird.sentry.io/issues/6269890787/?project=4505428124827648&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&statsPeriod=14d&stream_index=13
The text was updated successfully, but these errors were encountered:
Calculate the cipher length and base64 length ahead of time. (Fixes #853
45ba689
) We also fix up an existing issue with a user's schedules.details field.
62b605c
MelissaAutumn
Successfully merging a pull request may close this issue.
Encrypted fields are encrypted and then converted to base64 as noted here: https://github.com/kvesteri/sqlalchemy-utils/blob/master/sqlalchemy_utils/types/encrypted/encrypted_type.py#L114
We don't take into account the length of the additions from the cipher or base64 encoding. We should do that, and then update the strings and do a data migration to nuke a known case with schedule's detail field: https://thunderbird.sentry.io/issues/6269890787/?project=4505428124827648&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&statsPeriod=14d&stream_index=13
The text was updated successfully, but these errors were encountered: