We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
SQLAlchemy 2.0 is the latest and greatest in SQLAlchemy. it features
nullslast
nulls_last
anyway... here's the steps we need to do to migrate to SQLAlchemy 2.0
https://docs.sqlalchemy.org/en/14/changelog/migration_20.html
RemovedIn20Warning
future=True
__allow_unmapped__
The text was updated successfully, but these errors were encountered:
Given that I haven't heard anyone mention a warning in their code, I'd be fine defaulting SQLALCHEMY_WARN_20 to 1 for the live server.
Sorry, something went wrong.
MovedIn20Warning
Successfully merging a pull request may close this issue.
SQLAlchemy 2.0 is the latest and greatest in SQLAlchemy. it features
nullslast
tonulls_last
zero cost abstractionsanyway... here's the steps we need to do to migrate to SQLAlchemy 2.0
https://docs.sqlalchemy.org/en/14/changelog/migration_20.html
RemovedIn20Warning
sRemovedIn20Warning
sfuture=True
in the enginefuture=True
in the session__allow_unmapped__
to explicitly typed ORM models (https://docs.sqlalchemy.org/en/14/changelog/migration_20.html#migration-to-2-0-step-six-add-allow-unmapped-to-explicitly-typed-orm-models) (WE SHOULD DEFINITELY TYPE OUR MODELS)The text was updated successfully, but these errors were encountered: