Mike Bayer ebcb80be9c consider column.name directly when evaluating use_existing_column ...

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

2023-02-18 09:11:36 -05:00

..

aaa_profiling

move more Session weakref tests to test_memusage

2022-12-07 14:23:45 -05:00

base

port history meta to 2.0

2023-02-06 11:08:50 -05:00

dialect

prevent float tests from running on asyncmy

2023-02-15 18:28:12 -05:00

engine

do not return asyncio connections to the pool under gc

2023-02-06 16:09:33 -05:00

ext

modernize hybrids and apply typing

2023-02-16 18:01:31 -05:00

orm

consider column.name directly when evaluating use_existing_column

2023-02-18 09:11:36 -05:00

perf

Try running pyupgrade on the code

2022-11-16 23:03:04 +01:00

sql

Allow custom sorting of column in the ORM.

2023-02-16 19:21:43 -05:00

__init__.py

…

binary_data_one.dat

…

binary_data_two.dat

…

conftest.py

correct for pytest discovery

2022-03-04 16:28:31 -05:00

profiles.txt

pass more contextual information to PyWrapper param create

2022-12-27 14:04:19 -05:00

requirements.py

prevent float tests from running on asyncmy

2023-02-15 18:28:12 -05:00