upgrading for SQLAlchemy 2.0+#75
Conversation
|
Did you try this? The tests are not passing for me. I will take a look when I'll have the chance. |
|
I tested this code, you are right that some tests now fail. I have updated the conftest.py to use the 2.0 method of "execute" for SQLAlchemy, there are a few more tests to now individually work on, but I have pushed the changes to the "conftest" file for now. |
|
Sounds great - now the main question is - will the changes still work on 1.x? If not maybe it makes more sense to release 1.x as it is and then release 2.x with alchemy 2 compatibility. |
|
The actual code changes work on 1.X and 2.X, I haven’t checked the tests (yet). If the 2.0 method for engine execute is not backwards compatible to 1.X I imagine I can resolve this with a try/except code block.With the current code I have I have pushed there is one test failing on 2.X for group resource permissions, this may need your expertise as I have never used this service and don’t fully understand it.— LukeOn 11 Jan 2025, at 01:06, Marcin Lulek ***@***.***> wrote:
Sounds great - now the main question is - will the changes still work on 1.x? If not maybe it makes more sense to release 1.x as it is and then release 2.x with alchemy 2 compatibility.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
So my new changes ARE backwards compatible, so thats all good. The test error I also get on SQLAlchemy 1.4x, its on the test: All other tests pass fine, the error code for the failed test is: |
|
@ergo I have had another look, but still can't work out why this is failing, It may be todo with the way "outerjoin" now works in 2.0, but I can't see any issues with breaking changes on the changelog for it. |
Open for discussion, but think this is all that's needed, also backwards compatible.
@ergo any thoughts?