Treat single element ste vec as eql_v2_encrypted #122
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tobyhede
force-pushed
the
ste-vec-item-as-encrypted
branch
from
84a83c6 to
7fdcf3c
Compare
tobyhede
force-pushed
the
ste-vec-item-as-encrypted
branch
from
7fdcf3c to
d595344
Compare
freshtonic
approved these changes
Jul 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
An encrypted JSONB value contains an array of nested encrypted values for each indexed field path.
Where an SteVec has a single element, it can be treated as an
eql_v2_encryptedwhen compared in the various equality operators.This adds a check to the core
comparefunction that will "promote" the encrypted element of a single-element SteVec to an encrypted with meta data.