Hi, I've been testing out exposed 1.0.0 and the r2...

# exposed

[Wyatt Kennedy]

Hi, I've been testing out exposed 1.0.0 and the r2dbc support and ran into an issue. When I attempted to use a "referrersOn" to get the one to many relation, I get a compile time error on it's usage. Cannot access class 'SizedIterable'. Check your module classpath for missing or conflicting dependencies. I went and looked in the dependency and it explicitly mentions dependencies from the jdbc module. I don't see any mention in the documentation of the dao module only working for jdbc currently unless I'm just missing it

[Wyatt Kennedy]

I was crawling mentions of r2dbc and found the only mention of it not being compatible with dao yet was on the github readme. You might want to put that on the documentation somewhere.

[Viktor Kuzmin]

As mentioned eralier, r2dbc have big issues itself. And taking into account virtual threads, there is almost no sence to use r2dbc. At least from performance reasons.

[Pihentagy]

Huh? This is new to me. So shouldn't I use r2dbc, because its instable??

Aren't coroutines much faster than threads?

[Viktor Kuzmin]

Coroutines are not much faster in all situations. And you can achieve same or better performance with java virtual threads + jdbc, instead of r2dbc. The concept of r2dbc is really good, but r2dbc-pool, as I said, have some show stopper bugs.