linux/meta-openembedded.git/meta-python/recipes-devtools/python/python3-sqlalchemy_1.3.23.bb, branch kirkstone-next

python3-sqlalchemy: Upgrade 1.3.23 -> 1.4.2

2021-03-24T15:50:45+00:00

Upgrade to release 1.4.2: orm: - Added support for the declared_attr object to work in the context of dataclass fields. - Fixed issue in new ORM dataclasses functionality where dataclass fields on an abstract base or mixin that contained column or other mapping constructs would not be mapped if they also included a “default” key within the dataclasses.field() object. - Fixed regression where the Query.selectable accessor, which is a synonym for Query.__clause_element__(), got removed, it's now restored. - Fixed regression where use of an unnamed SQL expression such as a SQL function would raise a column targeting error if the query itself were using joinedload for an entity and was also being wrapped in a subquery by the joinedload eager loading process. - Fixed regression where the Query.filter_by() method would fail to locate the correct source entity if the Query.join() method had been used targeting an entity without any kind of ON clause. - Fixed regression where the SQL compilation of a Function would not work correctly if the object had been "annotated", which is an internal memoization process used mostly by the ORM. In particular it could affect ORM lazy loads which make greater use of this feature in 1.4. - Fixed regression where the ConcreteBase would fail to map at all when a mapped column name overlapped with the discriminator column name, producing an assertion error. The use case here did not function correctly in 1.3 as the polymorphic union would produce a query that ignored the discriminator column entirely, while emitting duplicate column warnings. As 1.4's architecture cannot easily reproduce this essentially broken behavior of 1.3 at the select() level right now, the use case now raises an informative error message instructing the user to use the .ConcreteBase._concrete_discriminator_name attribute to resolve the conflict. To assist with this configuration, .ConcreteBase._concrete_discriminator_name may be placed on the base class only where it will be automatically used by subclasses; previously this was not the case. engine: - Restored top level import for sqlalchemy.engine.reflection. This ensures that the base Inspector class is properly registered so that inspect() works for third party dialects that don't otherwise import this package. sql: - Fixed issue where using a func that includes dotted packagenames would fail to be cacheable by the SQL caching system due to a Python list of names that needed to be a tuple. - Fixed regression in the case() construct, where the "dictionary" form of argument specification failed to work correctly if it were passed positionally, rather than as a "whens" keyword argument. mypy: - Fixed issue in MyPy extension which crashed on detecting the type of a Column if the type were given with a module prefix like sa.Integer(). postgresql: - Rename the column name used by a reflection query that used a reserved word in some postgresql compatible databases. Signed-off-by: Leon Anavi Signed-off-by: Khem Raj Signed-off-by: Trevor Gamblin

python3-sqlalchemy: Upgrade 1.3.22 -> 1.3.23

2021-02-05T18:26:10+00:00

Upgrade to release 1.3.23: - Fixed bug where making use of the TypeEngine.with_variant() method on a TypeDecorator type would fail to take into account the dialect-specific mappings in use, due to a rule in TypeDecorator that was instead attempting to check for chains of TypeDecorator instances. - For SQLAlchemy 1.3 only, setup.py pins pg8000 to a version lower than 1.16.6. Version 1.16.6 and above is supported by SQLAlchemy 1.4. - Fixed issue where using Table.to_metadata() (called Table.tometadata() in 1.3) in conjunction with a PostgreSQL ExcludeConstraint that made use of ad-hoc column expressions would fail to copy correctly. - Casting to FLOAT is now supported in MySQL >= (8, 0, 17) and MariaDb >= (10, 4, 5). - Fixed bug where MySQL server default reflection would fail for numeric values with a negation symbol present. - Fixed long-lived bug in MySQL dialect where the maximum identifier length of 255 was too long for names of all types of constraints, not just indexes, all of which have a size limit of 64. As metadata naming conventions can create too-long names in this area, apply the limit to the identifier generator within the DDL compiler. - Fixed deprecation warnings that arose as a result of the release of PyMySQL 1.0, including deprecation warnings for the “db” and “passwd” parameters now replaced with “database” and “password”. - Fixed regression from SQLAlchemy 1.3.20 caused by a fix which adds double-parenthesis for MySQL functional expressions in indexes, as is required by the backend, this inadvertently extended to include arbitrary text() expressions as well as Alembic’s internal textual component, which are required by Alembic for arbitrary index expressions which don’t imply double parenthesis. The check has been narrowed to include only binary/ unary/functional expressions directly. - Fixed regression in Oracle dialect introduced by #4894 in SQLAlchemy 1.3.11 where use of a SQL expression in RETURNING for an UPDATE would fail to compile, due to a check for “server_default” when an arbitrary SQL expression is not a column. - Fixed bug in Oracle dialect where retriving a CLOB/BLOB column via Insert.returning() would fail as the LOB value would need to be read when returned; additionally, repaired support for retrieval of Unicode values via RETURNING under Python 2. - Fixed issue where the stringification that is sometimes called when attempting to generate the “key” for the .c collection on a selectable would fail if the column were an unlabeled custom SQL construct using the sqlalchemy.ext.compiler extension, and did not provide a default compilation form; while this seems like an unusual case, it can get invoked for some ORM scenarios such as when the expression is used in an “order by” in combination with joined eager loading. The issue is that the lack of a default compiler function was raising CompileError and not UnsupportedCompilationError. License-Update: Update year Signed-off-by: Leon Anavi Acked-by: Trevor Gamblin Signed-off-by: Khem Raj