Skip to content

Conversation

@onecrayon
Copy link
Owner

Closes #91. And what a pain in the butt implementing this was.

A lot of the find/replace code is minor AI slop; might want to go through and replace the generic stmt usage with something a little closer to my actual style, but for getting things up and running without needing to spend six hours or whatever of my own time doing incredibly boring find-and-replace, I'll take it.

Test suite is borked again; presumably the savepoint logic that I so painstakingly worked out for 1.4 just doesn't work for 2.0.
Through trial and error, I discovered that:

* Monkeypatching commit is no longer necessary (and in fact breaks things)
* `being_nested()` must be called on the connection
* Multiple sessions appear to be safer than passing a single session around
This module was a bit trickier; I was unfortunately unable to find a good way to nest SAVEPOINTs at three levels (e.g. could NOT get package -> module -> function nesting to properly incrementally roll back no matter what I tried), so now all deck tests share the same cards but rebuild their module-based stuff on a per-function basis.
Filtration test wasn't working; probably something to do with the database configuration, and I just don't really care to debug this one because it's a non-issue in production.
@onecrayon onecrayon merged commit f281a84 into main Aug 29, 2025
2 checks passed
@onecrayon onecrayon deleted the feature/sql-alchemy-upgrade branch August 29, 2025 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Maintenance: Upgrade to SQLAlchemy 1.4

2 participants