PublicArchive/sqlalchemy
2
0
Fork 0
mirror of https://github.com/sqlalchemy/sqlalchemy.git synced 2026-05-14 20:57:19 -04:00
Code Issues Packages Projects Releases Wiki Activity

note that 2.0 has behavioral changes outside of the 1.4->2.0 process

Browse Source 
Change-Id: I0ab9611c75f592acec73ca92271f970eae74d7ab
(cherry picked from commit 2c1550af60)
This commit is contained in:
Mike Bayer
2022-12-28 15:53:03 -05:00
parent afcbc3233b
commit 74becd0d35
1 changed files with 18 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/build/changelog/migration_20.rst
Vendored
+18 -3
View File
@@ -48,9 +48,12 @@ new ORM declarative system that unifies classical and declarative mapping,
support for Python dataclasses, and asyncio support for Core and ORM.
The steps to achieve 2.0 migration are in the following subsections; overall,
the general strategy is that once an application runs on 1.4 with all
warning flags turned on and does not emit any 2.0-deprecation warnings, it is
now cross-compatible with SQLAlchemy 2.0.
the general strategy is that once an application runs on 1.4 with all warning
flags turned on and does not emit any 2.0-deprecation warnings, it is now
**mostly** cross-compatible with SQLAlchemy 2.0. **Please note there may be
additional API and behavioral changes that may behave differently when running
against SQLAlchemy 2.0; always test code against an actual SQLAlchemy 2.0
release as the final step in migrating**.
First Prerequisite, step one - A Working 1.3 Application
@@ -468,6 +471,18 @@ that descend from ``Base``::
that don't use :class:`_orm.Mapped` to remain usable.
.. _migration_20_step_seven:
Migration to 2.0 Step Seven - Test against a SQLAlchemy 2.0 Release
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As mentioned previously, SQLAlchemy 2.0 has additional API and behavioral
changes that are intended to be backwards compatible, however may introduce
some incompatibilities nonetheless. Therefore after the overall porting
process is complete, the final step is to test against the most recent release
of SQLAlchemy 2.0 to correct for any remaining issues that might be present.
2.0 Migration - Core Connection / Transaction
=============================================