Skip to content

Parse#5

Merged
tobyhede merged 0 commit into
mainfrom
CIP-991/parse_handler
Dec 2, 2024
Merged

Parse#5
tobyhede merged 0 commit into
mainfrom
CIP-991/parse_handler

Conversation

@tobyhede

Copy link
Copy Markdown
Contributor

No description provided.

@tobyhede
tobyhede force-pushed the CIP-991/parse_handler branch from f491665 to 5f06229 Compare December 2, 2024 04:40
@tobyhede tobyhede changed the title Parse wip Parse Dec 2, 2024
@tobyhede
tobyhede merged this pull request into main Dec 2, 2024
@auxesis
auxesis deleted the CIP-991/parse_handler branch February 28, 2025 05:30
auxesis added a commit that referenced this pull request Mar 6, 2025
# This is the 1st commit message:

Initial commit (import from sql-mapper)

# This is the commit message #2:

First cut of public API

Call `eql_mapper::type_check(..)`

If successful, that returns a `TypedStatement` which describes:

1. the types & values of any literals that are destined to become EQL
   types and require encrypting
2. all of the expected params and their types
3. the type of the statement's projection (which will inform row
   decryption)

It is up to the caller to check the expected number of params is
correct, and arrange for all literals to be encrypted. Then call:

`TypedStatement::transform(encrypted_literals)`

which will return a new `Statement` with replaced literals.

# This is the commit message #3:

Make TypedStatement::literals a public field

# This is the commit message #4:

Ensure the actual types representing, um.. types are exported

# This is the commit message #5:

Add check to see if statement requires a transformation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant