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
When fetching where some_table.id = 1, the returned SomeTable#json is expected to be "{}" but it actually is "123,125". Not sure where that cryptic 123,125 comes from. According to https://stackoverflow.com/a/21343591/1225328, "123 and 125 is ascii for { and }", but not sure how this helps.
This appears to be a regression in R2DBC Borca-SR2. Things work fine with SR1. More specifically, the problem appears to be in 1.1.2 of the MariaDB driver. The problem does not occur with 1.1.1-rc, the version included in Borca-SR1.
Originally posted against Spring Boot: spring-projects/spring-boot#32485
MySQL:
Mapping:
When fetching where
some_table.id = 1
, the returnedSomeTable#json
is expected to be"{}"
but it actually is"123,125"
. Not sure where that cryptic123,125
comes from. According to https://stackoverflow.com/a/21343591/1225328, "123 and 125 is ascii for { and }", but not sure how this helps.According to wilkinsona:
Replicated in https://github.com/sp00m/spring-boot-2.7.4-r2dbc-json-issue, see https://github.com/sp00m/spring-boot-2.7.4-r2dbc-json-issue/blob/master/src/test/java/base/SomeTableRepositoryTest.java#L42 which passes with Spring Boot v2.7.3, but fails with v2.7.4:
The text was updated successfully, but these errors were encountered: