-
Notifications
You must be signed in to change notification settings - Fork 184
Add support for SPI Parameters #378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Milestone
Comments
mp911de
added a commit
that referenced
this issue
Jan 6, 2021
mp911de
added a commit
that referenced
this issue
Jan 6, 2021
mp911de
added a commit
that referenced
this issue
Jan 6, 2021
mp911de
added a commit
that referenced
this issue
Jan 6, 2021
mp911de
added a commit
that referenced
this issue
Jan 6, 2021
…ent null encoding with a given OID [#378]
mp911de
added a commit
that referenced
this issue
Jan 6, 2021
mp911de
added a commit
that referenced
this issue
Jan 6, 2021
mp911de
added a commit
that referenced
this issue
Feb 18, 2021
Use correct parameter type when assuming a specific Postgres OID. [#378]
mp911de
added a commit
that referenced
this issue
Feb 18, 2021
Use correct parameter type when assuming a specific Postgres OID. [#378]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
See r2dbc/r2dbc-spi#160.
We should extend our
PostgresqlObjectId
to implementType
so that it can be used together withParameters.in(…)
(e.g.Parameters.in(PostgresqlObjectId.CIRCLE)
) and we should propagate the desired data type to the encoded value. We also should allow dynamic type look up:so that runtime types can be used with our codecs.
The text was updated successfully, but these errors were encountered: