Add test coverage for go zero value reads writes #52
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.
When inserting a jsonb value as nil, or an empty map, or not including the field on insert, the value coming through to todb is an empty map[]. This is because go sets these values to the go zero value https://go.dev/ref/spec#The_zero_value.
This PR will add a change to check for this in the EncryptedJsonb type in goeql so that we don't serialize the value into the jsonb shape. The proxy will encrypt the value as "null", and will encrypt this. But, when trying to read, this error will return
handle] rewrite_results Error: Unknown variant code
11``.I have been testing by pointing to this branch locally cipherstash/goeql#3
I will do a release of goeql and then open this PR.Bumped goeql and ran tests: