Add TextEncryptedType to support large Text columns #730
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on
StringEncryptedType
, the only difference is SQLAlchemy treats it as aText
column instead of aString
(VARCHAR
in MySQL) column, allowing for far larger encrypted text data.This was made out of necessity when attempting to save encrypted Google OAuth tokens that cause the table size to exceed the max, even though individual columns were acceptable. By storing as
TEXT
(orBLOB
), they are stored separately and other than their metadata, don't count towards the table's max width.There is already a
EncryptedType
class usingLargeBinary
as the type, but it has a deprecation warning and comments warning that in the future it'll be changed toString
.