There are no R2DBC drivers for SQL Anywhere listed on https://r2dbc.io/drivers/. Auntie Google doesn't have anything useful to say when you search on "R2DBC" "SQL ANYWHERE" But as R2DBC is open source, and there already is a MS SQL driver, and SQL Anywhere speaks TDS, too, so how hard can it be to build a driver for SQL Anywhere? :)
(30 Mar '22, 03:22)
Volker Barth
Replies hidden
(30 Mar '22, 08:45)
Breck Carter
Well, before I wrote my comment, I had actually taken a look at the MS SQL driver code expecting I would be able to somehow grab how the real database connections are handled (or how they are bound to a known database API). But I was not successful. Probably that is the point of the "reactive approach" that it does not make use of an underlying common "blocking" DB API. Apparently I am not in the position to estimate how hard that really is if one is familiar with R2DBC...
(30 Mar '22, 09:04)
Volker Barth
|