Re: [sqlalchemy] Looking for help with interpreting an error/debugging

FWIW, after switching drivers I haven’t seen this issue again… (Please let’s not jinx it!) Jens On Monday, March 28, 2022 at 11:10:26 PM UTC+10 Mike Bayer wrote: > there's probably something up with that server so you will still get > errors, but at least they will be familiar looking > --

Re: [sqlalchemy] Looking for help with interpreting an error/debugging

there's probably something up with that server so you will still get errors, but at least they will be familiar looking On Mon, Mar 28, 2022, at 9:01 AM, jens.t...@gmail.com wrote: > Thank you Mike for your prompt response! I opened an issue CONPY-197 >

Re: [sqlalchemy] Looking for help with interpreting an error/debugging

Thank you Mike for your prompt response! I opened an issue CONPY-197 , let’s see what comes of that. I’ve used mysql+pymysql:// quite happily in the past with a MySQL db, and when we switched to MariaDB I switched the drivers. It didn’t occur to me

Re: [sqlalchemy] Looking for help with interpreting an error/debugging

hey there - never seen that before so it is very likely to be an issue specific to mariadbconnector, which is a much lesser-used driver. suggestions are to seek help from mariadb connector devs directly, in the interim try mysqlclient or pymysql to see if the issue resolves, or shows a better

[sqlalchemy] Looking for help with interpreting an error/debugging

Hello, I’m utterly stomped by this problem and I hope that the wisdom of the crowd (and the much more experienced users here) can point me into the right direction. I’ve got a single MariaDB (Ver 15.1 Distrib 10.6.5-MariaDB, for Linux (x86_64)) running natively on a