|
10 | 10 |
|
11 | 11 | .. changelog::
|
12 | 12 | :version: 2.0.41
|
13 |
| - :include_notes_from: unreleased_20 |
| 13 | + :released: May 14, 2025 |
| 14 | + |
| 15 | + .. change:: |
| 16 | + :tags: usecase, postgresql |
| 17 | + :tickets: 10665 |
| 18 | + |
| 19 | + Added support for ``postgresql_include`` keyword argument to |
| 20 | + :class:`_schema.UniqueConstraint` and :class:`_schema.PrimaryKeyConstraint`. |
| 21 | + Pull request courtesy Denis Laxalde. |
| 22 | + |
| 23 | + .. seealso:: |
| 24 | + |
| 25 | + :ref:`postgresql_constraint_options` |
| 26 | + |
| 27 | + .. change:: |
| 28 | + :tags: usecase, oracle |
| 29 | + :tickets: 12317, 12341 |
| 30 | + |
| 31 | + Added new datatype :class:`_oracle.VECTOR` and accompanying DDL and DQL |
| 32 | + support to fully support this type for Oracle Database. This change |
| 33 | + includes the base :class:`_oracle.VECTOR` type that adds new type-specific |
| 34 | + methods ``l2_distance``, ``cosine_distance``, ``inner_product`` as well as |
| 35 | + new parameters ``oracle_vector`` for the :class:`.Index` construct, |
| 36 | + allowing vector indexes to be configured, and ``oracle_fetch_approximate`` |
| 37 | + for the :meth:`.Select.fetch` clause. Pull request courtesy Suraj Shaw. |
| 38 | + |
| 39 | + .. seealso:: |
| 40 | + |
| 41 | + :ref:`oracle_vector_datatype` |
| 42 | + |
| 43 | + |
| 44 | + .. change:: |
| 45 | + :tags: bug, platform |
| 46 | + :tickets: 12405 |
| 47 | + |
| 48 | + Adjusted the test suite as well as the ORM's method of scanning classes for |
| 49 | + annotations to work under current beta releases of Python 3.14 (currently |
| 50 | + 3.14.0b1) as part of an ongoing effort to support the production release of |
| 51 | + this Python release. Further changes to Python's means of working with |
| 52 | + annotations is expected in subsequent beta releases for which SQLAlchemy's |
| 53 | + test suite will need further adjustments. |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | + .. change:: |
| 58 | + :tags: bug, mysql |
| 59 | + :tickets: 12488 |
| 60 | + |
| 61 | + Fixed regression caused by the DEFAULT rendering changes in version 2.0.40 |
| 62 | + via :ticket:`12425` where using lowercase ``on update`` in a MySQL server |
| 63 | + default would incorrectly apply parenthesis, leading to errors when MySQL |
| 64 | + interpreted the rendered DDL. Pull request courtesy Alexander Ruehe. |
| 65 | + |
| 66 | + .. change:: |
| 67 | + :tags: bug, sqlite |
| 68 | + :tickets: 12566 |
| 69 | + |
| 70 | + Fixed and added test support for some SQLite SQL functions hardcoded into |
| 71 | + the compiler, most notably the ``localtimestamp`` function which rendered |
| 72 | + with incorrect internal quoting. |
| 73 | + |
| 74 | + .. change:: |
| 75 | + :tags: bug, engine |
| 76 | + :tickets: 12579 |
| 77 | + |
| 78 | + The error message that is emitted when a URL cannot be parsed no longer |
| 79 | + includes the URL itself within the error message. |
| 80 | + |
| 81 | + |
| 82 | + .. change:: |
| 83 | + :tags: bug, typing |
| 84 | + :tickets: 12588 |
| 85 | + |
| 86 | + Removed ``__getattr__()`` rule from ``sqlalchemy/__init__.py`` that |
| 87 | + appeared to be trying to correct for a previous typographical error in the |
| 88 | + imports. This rule interferes with type checking and is removed. |
| 89 | + |
| 90 | + |
| 91 | + .. change:: |
| 92 | + :tags: bug, installation |
| 93 | + |
| 94 | + Removed the "license classifier" from setup.cfg for SQLAlchemy 2.0, which |
| 95 | + eliminates loud deprecation warnings when building the package. SQLAlchemy |
| 96 | + 2.1 will use a full :pep:`639` configuration in pyproject.toml while |
| 97 | + SQLAlchemy 2.0 remains using ``setup.cfg`` for setup. |
| 98 | + |
| 99 | + |
14 | 100 |
|
15 | 101 | .. changelog::
|
16 | 102 | :version: 2.0.40
|
|
0 commit comments