Replies: 1 comment 1 reply
-
This is a bug. I'll transfer into the issue list. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, due to the limit on the record size I implemented a compressed field on my table , it should behave similar to crypt logic but compress on write and uncompress on reads, for that I used the table transform method with following logic:
But I discovered that when I call
await model.create({ content: 'Very Large String' });
the returned value of the create method is the value parsed aswrite
which means it returns the object with compressed string value, to circumvent that I need to perform aget
aftercreate
so it returns the uncompressed value.That makes me think if the returned value of
create
/update
should also be parsed as read after executing the operation on database.WDYT?
Beta Was this translation helpful? Give feedback.
All reactions