You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an example, if the query has a parameter of type interval, mapped by io.vertx.pgclient.data.Interval, and the user puts a java.time.Duration, then PgClient will set the value to NULL.
Fixeseclipse-vertx#1463
With this change, a DataType always has a param extractor.
The default extractor signals the failure to convert to PgParamDesc.
Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
Fixeseclipse-vertx#1463
With this change, a DataType always has a param extractor.
The default extractor signals the failure to convert to PgParamDesc.
Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
#1464)
Fixes#1463
With this change, a DataType always has a param extractor.
The default extractor signals the failure to convert to PgParamDesc.
Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
eclipse-vertx#1464)
Fixeseclipse-vertx#1463
With this change, a DataType always has a param extractor.
The default extractor signals the failure to convert to PgParamDesc.
Signed-off-by: Thomas Segismont <tsegismont@gmail.com>
Originally reported in #1281
As an example, if the query has a parameter of type
interval
, mapped byio.vertx.pgclient.data.Interval
, and the user puts ajava.time.Duration
, then PgClient will set the value toNULL
.It happens here:
vertx-sql-client/vertx-pg-client/src/main/java/io/vertx/pgclient/impl/codec/PgParamDesc.java
Lines 53 to 62 in cc9803f
We would expect the client to reject the query using a message generated by
buildWhenArgumentsTypeNotMatched
.But the
INTERVAL
data type is defined without a type extractor:So the client invokes
values.get(paramDataType.encodingType, i);
And there the returned value is null because
Interval
is not assignable fromDuration
:vertx-sql-client/vertx-sql-client/src/main/java/io/vertx/sqlclient/Tuple.java
Lines 1716 to 1719 in 2de7f0d
The text was updated successfully, but these errors were encountered: