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

Should we fallback to SQLAlchemy ORM asyncio? #595

Closed
foxmask opened this issue Oct 30, 2024 · 1 comment
Closed

Should we fallback to SQLAlchemy ORM asyncio? #595

foxmask opened this issue Oct 30, 2024 · 1 comment

Comments

@foxmask
Copy link

foxmask commented Oct 30, 2024

Hi,
In the doc https://www.starlette.io/database/ , you explain we can use GINO as an async ORM solution with sqlalchemy, but it seems databases requires sqlalchemy>=2.0.7 and gino requires sqlalchemy < 1.4

pip install gino
Collecting gino
  Downloading gino-1.0.1-py3-none-any.whl.metadata (4.9 kB)
Collecting SQLAlchemy<1.4,>=1.2.16 (from gino)

[...]
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
databases 0.9.0 requires sqlalchemy>=2.0.7, but you have sqlalchemy 1.3.24 which is incompatible.

I also try https://github.com/encode/orm but does not seem to enjoy sqlalchemy >= 2 too encode/orm#168

do you have some advice about SQLAlchemy ORM Asyncsio https://docs.sqlalchemy.org/en/20/orm/examples.html ?

thanks

@foxmask foxmask changed the title Should we fallback to SQLalchemy asyncio? Should we fallback to SQLAlchemy ORM asyncio? Oct 30, 2024
@foxmask
Copy link
Author

foxmask commented Oct 30, 2024

forget that I'll do differently

@foxmask foxmask closed this as completed Oct 30, 2024
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

No branches or pull requests

1 participant