A way around io.vertx.sqlclient.Row returning boolean columns as Byte.

[Olofu Mark]

We moving to the reactive MySQL Client.

the legacy JDBC Client was returning boolean columns as boolean which was pretty what we want. 

io.vertx.sqlclient.Row is returning boolean columns in its raw form(i understand that mysql stores a boolean as tinyint) which breaks all our front end applications.

is there a way around it? i.e to retrieve boolean columns as java boolean?

Thanks.

[Olofu Mark]

thought this would work but it didn't.

connectOptions.addProperty("tinyInt1isBit", "false");

[Olofu Mark]

these also didn't work.

        connectOptions.addProperty("tinyInt1isBit", "true");
        connectOptions.addProperty("transformedBitIsBoolean", "true");

[Thomas SEGISMONT]

https://vertx.io/docs/vertx-mysql-client/java/#_handling_boolean

It is stored in the row or tuple as a java.lang.Byte but you can get the boolean value with Row.getBoolean

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+un...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/0ba87e40-0e1c-4916-8c30-2557920cc6fbn%40googlegroups.com.

[Olofu Mark]

We stream Row#toJson() to clients without modifications.

Trying to avoid the overhead of first reading individual columns as boolean and then manually reinserting into the Json.

Thanks anyway.

Everything else seems great.

Please how does one observe what's going on in the connection pool, see connections state?

[Thomas SEGISMONT]

Observability of the pool is provided with Vert.x Metrics (e.g. https://vertx.io/docs/vertx-micrometer-metrics/java/) and Vert.x Tracing (https://vertx.io/docs/vertx-opentelemetry/java/)

To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/9699361c-260b-4b4e-b584-3aa746b6c844n%40googlegroups.com.

[Olofu Mark]

Thanks Thomas,

Please would like to understand a bit more:

Given that Row.getBoolean is already possible, wouldn't it be more useful to have rows return booleans out of the box based on our own configuration?

is there a deeper reason why this is currently unavailable?

i.e with the understanding that it requires less code and makes things a lot easier instead of calling getBoolean repeatedly to achieve what i earlier described.

(for despite being the underlying storage type, Byte isn't very useful on its own.)

[Thomas SEGISMONT]

Feel free to file a request for enhancement to the vertx-sql-client, then we'll talk about it with the maintainer.