New release of DBXS today: https://pypi.org/project/dbxs/2026.5.20/
This is a very minor release with a small tweak to its SQLAlchemy Core support so that `.returning()` statements don't cause a spurious type error.
Discussion
New release of DBXS today: https://pypi.org/project/dbxs/2026.5.20/
This is a very minor release with a small tweak to its SQLAlchemy Core support so that `.returning()` statements don't cause a spurious type error.
"Wait… SQLAlchemy Core Support?", I hear you ask. Yes, #DBXS supports #SQLAlchemy Core, and has done so for quite some time. This was previously undocumented so I can certainly forgive you for not knowing.
So the *real* story of this release is not so much any big code changes, but rather updated dependency testing as well as *comprehensive documentation* for the SQLAlchemy feature. This may teach you a few things you didn't know about #Python database support. https://dbxs.readthedocs.io/en/latest/howto.html#sqlalchemy-core-support
For example, did you know that since Python has no cross-database way of specifying a prepared SQL statement, that it will take the comparatively much slower path of just re-uploading the same SQL string over and over again, if that string varies at all? And that it's *very* easy to trigger this failure mode with SQLAlchemy because there's nothing to suggest to you that you should not be dropping Python constant objects into the middle of your expressions?
Also, did you know that manually constructing SQLAlchemy queries in the body of functions consumes *substantially* more CPU and memory resources in your application than pre-computing them at import time? And that SQLAlchemy has a bindparam() object specifically to facilitate this much more efficient mode of operation?