Yoann Rodière
Yoann Rodière
Guy, please read my answer :) > So what I'm asking is why can't the driver be configured the same way we configure database connection and can only be hardcoded?...
> we would need a way to set the OpenTelemetry / OpenTracing JDBC support differently Right. That being said, we don't seem to be doing much at build-time with the...
> If the DB driver is for the same DB, except for tracing support, no need to change the driver in the runtime env. Always use the driver with tracing...
@radcortez I think @OleKsimov is aware OpenTracing is deprecated, as (from what I understand) they wanted this precisely for migration purposes, from OpenTracing to OpenTelemetry. Anyway, if you consider this...
Also reported as #25836 by [rmanibus](https://github.com/rmanibus) with a separate reproducer and (probably) a more recent version of Quarkus: > Reproducer: https://github.com/rmanibus/quarkus_25836 > > It's not the same error than in...
FWIW, a workaround would be to configure a log filter: https://quarkus.io/guides/logging#console-log-handler You can do it for the console (`quarkus.log.console.filter`) but also for the file logging (`quarkus.log.file.filter`). Though we'd probably want...
Not a fan of configuration properties that change the behavior of APIs so drastically, but in this case... It might be the way forward. Let me explain: I would argue...
> I don't think the different default compared to the annotations is an issue, as they are very different API's. I get that `UserTransaction.begin()` always starts a new transaction, and...
Thanks @stuartwdouglas . I assume in your example, you expect `doSomething` to be called with an existing transaction already active, somehow? Okay, I understand. It would indeed be pretty confusing...
> Maybe we should start a thread on the dev list? Right, will do.