sql: use ScalarType
rather than mz_pgrepr::Type
as param type
#10619
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.
The
mz_pgrepr::Type
is a PostgreSQL implementation detail but hadleaked into the Materialize-specific
sql
andcoord
crates. Correctthat boundary violation. The code to take a
mz_pgrepr::Value
into aDatum
gets much simpler in the process; thepgrepr::Type
type is nowdirectly convertible to a
ScalarType
without looking at the datumsinvolved, so we can massively simplify the signature of
Value::into_datum
and entirely removepgrepr::null_datum
.Motivation
Checklist