Skip to content
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

Make mikado compatible with Sqlalchemy 1.4.0 and following #388

Closed
lucventurini opened this issue Mar 17, 2021 · 3 comments · Fixed by #419
Closed

Make mikado compatible with Sqlalchemy 1.4.0 and following #388

lucventurini opened this issue Mar 17, 2021 · 3 comments · Fixed by #419

Comments

@lucventurini
Copy link
Collaborator

lucventurini commented Mar 17, 2021

Version 2.2.1 introduces a pin for https://github.com/kvesteri/sqlalchemy-utils as it is incompatible with SQLAlchemy 1.4.0 and newer.

This pin should be removed as soon as sqlalchemy-utils is updated with a patch introducing the compatibility.

@lucventurini
Copy link
Collaborator Author

lucventurini commented Mar 17, 2021

Please note that the bioconda/bioconda-recipes meta.yaml file will also need to be updated, removing the pin, once sqlalchemy-utils is updated.

@lucventurini lucventurini changed the title Remove the pin for SQLAlchemy [IN PROGRESS] Make mikado compatible with Sqlalchemy 1.4.0 and following Mar 18, 2021
@lucventurini
Copy link
Collaborator Author

Update: I have revised the release notes for SQLA 1.4.0 and ... Mikado will need lots of work to be made compatible. Many constructs that are used in the code have been deprecated (session.query, baked queries to name two).

This would require dedicated work.

@lucventurini
Copy link
Collaborator Author

Update: sqlalchemy-utils now supports SQLA 1.4+, from 0.37 (present in PyPI but not Conda).
The pin on sqlalchemy can now be removed if sqlalchemy-utils is enforced to 0.37 and later.

ljyanesm added a commit that referenced this issue Aug 5, 2021
- Updates implicitly converted scalar queries in orf and junctions.
- Removes "threadlocal" strategy from the engine connection parameters in xml_serialiser.py as this is not supported.

Fixes #388
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants