.. change::
:tags: bug, schema
:tickets: 5919
+ :versions: 1.4.0
Repaired / implemented support for primary key constraint naming
conventions that use column names/keys/etc as part of the convention. In
.. change::
:tags: bug, engine
:tickets: 5929
+ :versions: 1.4.0
Fixed bug where the "schema_translate_map" feature failed to be taken into
account for the use case of direct execution of
.. change::
:tags: bug, orm
:tickets: 5952
+ :versions: 1.4.0
Fixed issue where the process of joining two tables could fail if one of
the tables had an unrelated, unresolvable foreign key constraint which
would raise :class:`_exc.NoReferenceError` within the join process, which
nonetheless could be bypassed to allow the join to complete. The logic
- which tested the exception for signficance within the process would make
+ which tested the exception for significance within the process would make
assumptions about the construct which would fail.
.. change::
:tags: bug, orm
:tickets: 5983
+ :versions: 1.4.0
Removed very old warning that states that passive_deletes is not intended
for many-to-one relationships. While it is likely that in many cases
.. change::
- :tags: bug, orm, postgresql
+ :tags: bug, postgresql
:tickets: 5989
+ :versions: 1.4.0
- Fixed issue where using :class:`_ext.aggregate_order_by` would return
- ARRAY(NullType) under certain conditions.
+ Fixed issue where using :class:`_postgresql.aggregate_order_by` would
+ return ARRAY(NullType) under certain conditions, interfering with
+ the ability of the result object to return data correctly.
.. change::
:tags: bug, orm
:tickets: 6001
+ :versions: 1.4.0
Fixed issue where the :class:`_mutable.MutableComposite` construct could be
placed into an invalid state when the parent object was already loaded, and
.. change::
:tags: bug, sql, sqlite
:tickets: 6007
+ :versions: 1.4.0
Fixed issue where the CHECK constraint generated by :class:`_types.Boolean`
or :class:`_types.Enum` would fail to render the naming convention