delta/python-packages/sqlalchemy.git/lib/sqlalchemy, branch ticket_5648

ensure event handlers called for all do_ping

2023-03-01T21:20:36+00:00

The support for pool ping listeners to receive exception events via the
:meth:`.ConnectionEvents.handle_error` event added in 2.0.0b1 for
:ticket:`5648` failed to take into account dialect-specific ping routines
such as that of MySQL and PostgreSQL. The dialect feature has been reworked
so that all dialects participate within event handling.   Additionally,
a new boolean element :attr:`.ExceptionContext.is_pre_ping` is added
which identifies if this operation is occurring within the pre-ping
operation.

For this release, third party dialects which implement a custom
:meth:`_engine.Dialect.do_ping` method can opt in to the newly improved
behavior by having their method no longer catch exceptions or check
exceptions for "is_disconnect", instead just propagating all exceptions
outwards. Checking the exception for "is_disconnect" is now done by an
enclosing method on the default dialect, which ensures that the event hook
is invoked for all exception scenarios before testing the exception as a
"disconnect" exception. If an existing ``do_ping()`` method continues to
catch exceptions and check "is_disconnect", it will continue to work as it
did previously, but ``handle_error`` hooks will not have access to the
exception if it isn't propagated outwards.

Fixes: #5648
Change-Id: I6535d5cb389e1a761aad8c37cfeb332c548b876d

add notes to all mapper flush events that these are only for flush

2023-02-21T16:00:03+00:00

Fixes: #9339
Change-Id: I44542166417776733245e2ba39cd5de89b6d748b

Fix the docstring of AppenerQuery.append() (#9336)

2023-02-20T20:05:09+00:00

Fix a syntax error in `AsyncConnection.stream_scalars()` example. (#9334)

2023-02-19T16:47:33+00:00

consider column.name directly when evaluating use_existing_column

2023-02-18T14:11:36+00:00

Fixed issue where new :paramref:`_orm.mapped_column.use_existing_column`
feature would not work if the two same-named columns were mapped under
attribute names that were differently-named from the explicit name given to
the column itself. The attribute names can now be differently named when
using this parameter.

Fixes: #9332
Change-Id: I43716b8ca2b089e54a2b078db28b6c4770468bdd

more edits

2023-02-17T16:25:16+00:00

I can only see issues in the docs when they're live on the
site, sorry

Change-Id: I948b7c8e37657ca85d02843211cbfdb03aa5da75

typo, captions

2023-02-17T16:23:41+00:00

Change-Id: I547e66b60f5a7b2901a76ebc59469bce018e05ff

Version 2.0.5 placeholder

2023-02-17T16:01:43+00:00

rework hybrid docs further

2023-02-17T15:24:32+00:00

we have a very complicated story to tell and we need to
keep it within "reference doc" mode as much as we can

Change-Id: I873b7d95aea7b5a1d04de0c78a4e88651c908b35

Allow custom sorting of column in the ORM.

2023-02-17T00:21:43+00:00

To accommodate a change in column ordering used by ORM Declarative in
SQLAlchemy 2.0, a new parameter :paramref:`_orm.mapped_column.sort_order`
has been added that can be used to control the order of the columns defined
in the table by the ORM, for common use cases such as mixins with primary
key columns that should appear first in tables. The change notes at
:ref:`change_9297` illustrate the default change in ordering behavior
(which is part of all SQLAlchemy 2.0 releases) as well as use of the
:paramref:`_orm.mapped_column.sort_order` to control column ordering when
using mixins and multiple classes (new in 2.0.4).

Fixes: #9297
Change-Id: Ic7163d64efdc0eccb53d6ae0dd89ec83427fb675