-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support to SQLAlchemy 2.0 #326
Comments
Any ideas of the scope of work required for this and/or when it will be tackled? :) |
This is still just experimental but so far I had to make those changes:
|
There is another issue with the polymorphic_on check in
|
Bump 💪 |
Hi sorry, will look at this shortly |
Bump 🙂 |
Bump 🚀 |
If this isn't going to be address any time soon, could y'all at least update setup.py to exclude incompatible versions of dependencies as a stopgap? I just checked out the repo to see if I could get a PR together, but I can't even run the tests because of a problem with flask-sqlalchemy.
|
Got a PR up to address this. Dealing with a few broken tests and some hanging with postgres. I don't have much experience with sqlalchemy, so any help figuring out the problem would be greatly appreciated. |
Hi all, thanks very much for your help. I'm working through the suggested changes and the other issues that are currently causing tests to break but it's taken longer than expected. In the meantime, I've raised #332 in case anyone has opinions on that. |
Just to update here, I'm having trouble with the postgres dialect (particularly the new executemany code, which now appears to be a single query), so I'll have to park this for a few days. |
SQLAlchemy-Continuum is currently none functional with SQLAlchemy 2.0: kvesteri/sqlalchemy-continuum#331 kvesteri/sqlalchemy-continuum#326
Right, I've pushed to the sqla-2.0 branch and tests are passing except for the native ones. Is anyone able to have a look through for any issues? This version only supports SQLAlchemy >= 1.4, but I figure that's reasonable as it's the transitional version and 1.3 is EOL. Still to do:
I'll also be renaming the master branch to main with this release, just so people are aware. |
Do we have any updates on this? |
I was hoping someone would be able to give it a test with their code, but failing that I'll probably do a release next week. |
@marksteward I'm happy to help in whatever is needed to get this released, just let me know. |
FYI tested the WIP branch in a personal project with SA and PostgreSQL, seems to be working fine. |
Hi. Do we have any updates? |
I've tested on this branch: https://github.com/kvesteri/sqlalchemy-continuum/tree/sqla-2.0 ... seems to be working fine for PostgreSQL. @marksteward what's needed to release this? |
I'm happy to contribute to whatever we need to get this done. |
Thanks! I'm about to cut a 1.4 release, but if you want to work out any outstanding 2.0 warnings that'd be great. I'm expecting to have to make some patch releases soon after this. Also, I've just realised I don't have permission to rename master to main. @kvesteri can you do that? |
OK, I've published 1.4. Please give it a go! |
Thanks @marksteward! Will keep testing now with this release |
No description provided.
The text was updated successfully, but these errors were encountered: