41aa879a20
- update to 2.0.16: * Python 3.12 support * Fixed regression in the 2.0 series where the default value of validates.include_backrefs got changed to False for the validates() function * Unified the custom PostgreSQL operator definitions * Added support for PostgreSQL 10 NULLS NOT DISTINCT feature of unique indexes and unique constraints * Use proper precedence on PostgreSQL specific operators, such as @> * see https://docs.sqlalchemy.org/en/20/changelog/changelog_20.html#change-2.0.16Dirk Mueller2023-06-19 20:25:19 +00:00
2fe3a99f0d
- update to 1.4.41: * Fixed issue where use of the :func:_sql.table construct, passing a string for the :paramref:_sql.table.schema parameter, would fail to take the "schema" string into account when producing a cache key, thus leading to caching collisions if multiple, same-named :func:_sql.table constructs with different schemas were used. * Fixed event listening issue where event listeners added to a superclass would be lost if a subclass were created which then had its own listeners associated. The practical example is that of the :class:.sessionmaker class created after events have been associated with the :class:_orm.Session class. * Hardened the cache key strategy for the :func:_orm.aliased and :func:_orm.with_polymorphic constructs. While no issue involving actual statements being cached can easily be demonstrated (if at all), these two constructs were not including enough of what makes them unique in their cache keys for caching on the aliased construct alone to be accurate. * Fixed regression appearing in the 1.4 series where a joined-inheritance query placed as a subquery within an enclosing query for that same entity would fail to render the JOIN correctly for the inner query. The issue manifested in two different ways prior and subsequent to version 1.4.18 (related issue 🎫6595), in one case rendering JOIN twice, in the other losing the JOIN entirely. To resolve, the conditions under which "polymorphic loading" are applied have been scaled back to not be invoked for simple joined inheritance queries. * Fixed issue in :mod:sqlalchemy.ext.mutable extension where collection links to the parent object would be lost if the object were merged with :meth:.Session.merge while also passing :paramref:.Session.merge.load as False. * Fixed issue involving :func:_orm.with_loader_criteria where a closure variable used as bound parameter value within the lambda would not carry
Dirk Mueller2022-09-17 07:30:16 +00:00
7e0b551e77
- update to 1.4.37 * details on https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-1.4.37 * Fixed issue where using a column_property() construct containing a subquery against an already-mapped column attribute would not correctly apply ORM-compilation behaviors to the subquery, including that the “IN” expression added for a single-table inherits expression would fail to be included. * Fixed issue where ORM results would apply incorrect key names to the returned Row objects in the case where the set of columns to be selected were changed, such as when using Select.with_only_columns(). * Fixed bug, likely a regression from 1.3, where usage of column names that require bound parameter escaping, more concretely when using Oracle with column names that require quoting such as those that start with an underscore, or in less common cases with some PostgreSQL drivers when using column names that contain percent signs, would cause the ORM versioning feature to not work correctly if the versioning column itself had such a name, as the ORM assumes certain bound parameter naming conventions that were being interfered with via the quotes. This issue is related to #8053 and essentially revises the approach towards fixing this, revising the original issue #5653 that created the initial implementation for generalized bound-parameter name quoting.
Dirk Mueller2022-06-04 08:51:19 +00:00
da9501e87f
- update to 1.4.36: * details on https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html#change-1.4.36 * Fixed regression where the change made for #7861, released in version 1.4.33, that brought the Insert construct to be partially recognized as an ORM-enabled statement * Modified the DeclarativeMeta metaclass to pass cls.__dict__ into the declarative scanning process to look for attributes, rather than the separate dictionary passed to the type’s __init__() method * Fixed a memory leak in the C extensions which could occur when calling upon named members of Row when the member does not exist under Python 3 * Added a warning regarding a bug which exists in the Result.columns() method when passing 0 for the index in conjunction with a Result that will return a single ORM entity, which indicates that the current behavior of Result.columns() is broken in this case as the Result object will yield scalar values and not Row objects * Fixed bug where ForeignKeyConstraint naming conventions using the referred_column_0 naming convention key would not work if the foreign key constraint were set up as a ForeignKey object rather than an explicit ForeignKeyConstraint object.
Dirk Mueller2022-05-04 19:57:32 +00:00
ad0e633eae
- update to version 1.4.26: * a repair to the workings of the update() statement in an ORM context when used with hybrid and composite attributes. * Fixes for the with_loader_criteria() ORM option * adjustments to the ORM Session interface to accommodate for new API features * some new legacy warnings for lesser used patterns with Query.join() * SQL / ORM fixes for the use case of selecting from repeated, non-labeled column expressions, typically the null() construct when used as a placeholder in a UNION statement. * For PostgreSQL, refinements to the "expanding IN" SQL feature when used with PostgreSQL ARRAY datatypes as well as fixes for the mostly PostgreSQL-specific any_() and all_() column methods. * For MySQL, repaired support for new behaviors in MariaDB 10.6 * For SQL Server, reflection fixes and improvements for foreign key constraints as well table /view detection.
Dirk Mueller2021-10-27 20:33:19 +00:00
16e4a5ea78
- update to version 1.4.25: * Fixed regression due to 🎫7024 where the reorganization of the "platform machine" names used by the `greenlet dependency mis-spelled "aarch64" and additionally omitted uppercase "AMD64" as is needed for Windows machines. * Fixed a bug in :meth:_asyncio.AsyncSession.execute and :meth:_asyncio.AsyncSession.stream that required execution_options to be an instance of immutabledict when defined. It now correctly accepts any mapping. * Improve the interface used by adapted drivers, like the asyncio ones, to access the actual connection object returned by the driver. * Implemented missing methods in :class:_functions.FunctionElement which, while unused, would lead pylint to report them as unimplemented abstract methods. * Fixed an issue where :meth:_reflection.has_table returned True for local temporary tables that actually belonged to a different SQL Server session (connection). An extra check is now performed to ensure that the temp table detected is in fact owned by the current session. * Fixed issue where the ability of the :meth:_events.ConnectionEvents.before_execute method to alter the SQL statement object passed, returning the new object to be invoked, was inadvertently removed. This behavior has been restored. * Ensure that str() is called on the an :paramref:_url.URL.create.password argument, allowing usage of objects that implement the __str__() method as password attributes. Also clarified that one such object is not appropriate to dynamically change the password for each database connection; the approaches at :ref:engines_dynamic_tokens should be used instead. * Fixed ORM issue where column expressions passed to query()` or
Dirk Mueller2021-10-16 23:39:38 +00:00
096aa562dd
Accepting request 890933 from home:alarrosa:branches:devel:languages:python
Markéta Machová2021-05-07 08:54:47 +00:00
9c1e4fc47c
Accepting request 890784 from home:alarrosa:branches:devel:languages:python
Matej Cepl2021-05-05 18:48:40 +00:00
2ed7a610f4
Accepting request 890304 from home:alarrosa:branches:devel:languages:python
Dirk Mueller2021-05-04 10:53:23 +00:00
cfc7ff55e8
Accepting request 874679 from devel:languages:python
Richard Brown
2021-03-02 13:43:04 +00:00
17ba961611
Accepting request 874678 from home:mcepl:branches:python36
Matej Cepl2021-02-23 18:38:02 +00:00
a5daba2c4f
- update to 1.3.23: * Release 1.3.23 contains an array of bugfixes specific to dialects such as Oracle, PostgreSQL, and MySQL.
Dirk Mueller2021-02-23 17:08:06 +00:00
ed31d819bb
Accepting request 842694 from system:homeautomation:home-assistant:unstable
Tomáš Chvátal
2020-10-20 07:53:08 +00:00
0d6fd6dc04
- Replace pytest_depr_from_parent.patch with the upstream commit resolving same issue (gh#sqlalchemy/sqlalchemy#commit40cdb9c0bf4d).
Matej Cepl2020-10-09 13:52:28 +00:00
cf13b151ec
- Add pytest_depr_from_parent.patch to fix FTBGS with pytest 6.* (gh#sqlalchemy/sqlalchemy#5635)
Matej Cepl2020-10-08 15:45:35 +00:00
f668cbb37b
- update to 1.3.19 * Adjusted the workings of the Mapper.all_orm_descriptors() * The name of the virtual column used when using the AbstractConcreteBase and ConcreteBase classes can now be customized * Repaired an issue where the “ORDER BY” clause rendering a label name rather than a complete expression * The LookupError message will now provide the user with up to four possible values that a column is constrained to via the Enum * Fixed issue where the Connection.execution_options.schema_translate_map feature would not take effect when the Sequence.next_value() function for a Sequence were used in the Column.server_default parameter and the create table DDL were emitted. * Added a **kw argument to the DeclarativeMeta.__init__() method
Ondřej Súkup2020-08-20 12:04:06 +00:00