>> A JDBC suprocess is a
>> matter of coding one, so it's the problem of whoever will code it :)
>> Where's the harm if someone does the work?
>
> There isn't; I'm just concerned about spending our limited total available
> time/effort on things that don't actually have to be done.  But if you are
> fired up about it, far be it from me to stop you.

That's a good concern to have. We are doing very many with very few
people. However, a subprocess driver can be written in a high-level
language in a matter of hours. C took a day because it's C. Of course,
ongoing maintenance takes a nonzero amount of time too, but it's a drop
in the bucket compared to everything else we do. Even the C drivers are
fast to update once the S-expression plumbing is in place. I haven't had
any substantial problems with them yet.

Just looked up JDBC's Wikipedia page and there's a bridge to access ODBC
via JDBC, lol. So we come full circle to the start of this mailing list.
Of course, there is probably JDBC and ODBC access to MariaDB CONNECT...