summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge "disable polymorphic adaption in most cases" into mainmike bayer2022-12-089-75/+508
|\
| * disable polymorphic adaption in most casesMike Bayer2022-12-079-75/+508
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Improved a fix first made in version 1.4 for :ticket:`8456` which scaled back the usage of internal "polymorphic adapters", that are used to render ORM queries when the :paramref:`_orm.Mapper.with_polymorphic` parameter is used. These adapters, which are very complex and error prone, are now used only in those cases where an explicit user-supplied subquery is used for :paramref:`_orm.Mapper.with_polymorphic`, which includes only the use case of concrete inheritance mappings that use the :func:`_orm.polymorphic_union` helper, as well as the legacy use case of using an aliased subquery for joined inheritance mappings, which is not needed in modern use. For the most common case of joined inheritance mappings that use the built-in polymorphic loading scheme, which includes those which make use of the :paramref:`_orm.Mapper.polymorphic_load` parameter set to ``inline``, polymorphic adapters are now no longer used. This has both a positive performance impact on the construction of queries as well as a substantial simplification of the internal query rendering process. The specific issue targeted was to allow a :func:`_orm.column_property` to refer to joined-inheritance classes within a scalar subquery, which now works as intuitively as is feasible. ORM context, mapper, strategies now use ORMAdapter in all cases instead of straight ColumnAdapter; added some more parameters to ORMAdapter to make this possible. ORMAdapter now includes a "trace" enumeration that identifies the use path for the adapter and can aid in debugging. implement __slots__ for the ExternalTraversal hierarchy up to ORMAdapter. Within this change, we have to change the ClauseAdapter.wrap() method, which is only used in one polymorphic codepath, to use copy.copy() instead of `__dict__` access (apparently `__reduce_ex__` is implemented for objects with `__slots__`), and we also remove pickling ability, which should not be needed for adapters (this might have been needed for 1.3 and earlier in order for Query to be picklable, but none of that state is present within Query / select() / etc. anymore). Fixes: #8168 Change-Id: I3f6593eb02ab5e5964807c53a9fa4894c826d017
* | Oracle COLUMN_VALUE is a column name, not a keywordMike Bayer2022-12-076-14/+58
|/ | | | | | | | | Fixed issue in Oracle compiler where the syntax for :meth:`.FunctionElement.column_valued` was incorrect, rendering the name ``COLUMN_VALUE`` without qualifying the source table correctly. Fixes: #8945 Change-Id: Ia04bbdc68168e78b67a74bb3834a63f5d5000627
* move more Session weakref tests to test_memusageMike Bayer2022-12-072-161/+169
| | | | | | | | py311 may be more sensitive here, or maybe the machines are acting differently these days, in any case move memory / GC sensitive tests to test_memusage. Change-Id: I218295150efc2f7ea88da9960ff10fda63dc60b1
* sort materialize view names in testMike Bayer2022-12-061-1/+1
| | | | | | saw this fail on CI with views in reverse order Change-Id: I953f379f36924673a49b94cf5e7f54d071044113
* take mariadb-connector out of dbapi main jobMike Bayer2022-12-061-1/+2
| | | | | | | | | | | | | | mariadb-connector seems to have their release situation "fixed", but for 1.1.5post3 they are requiring mariadb-connector-c 3.3.1, Fedora 36 which is quite bleeding edge only has 3.2.7. There's no way we can easily have a version specifier that will look at underlying client libraries. since mariadb-connector's main branch seems to work way ahead of where we will normally have client libraries set up, it's not really worth testing in CI right now. Change-Id: Idcb034da6d06620b5e212582bbc63a246a9fe58b
* Version 2.0.0b5 placeholderMike Bayer2022-12-052-1/+5
|
* - 2.0.0b4rel_2_0_0b4Mike Bayer2022-12-0525-297/+320
|
* Merge "Add tests for issue #8168; slight internal adjustments" into mainmike bayer2022-12-054-11/+161
|\
| * Add tests for issue #8168; slight internal adjustmentsMike Bayer2022-12-054-11/+161
| | | | | | | | | | | | | | | | | | | | | | | | | | The issue in #8168 was improved, but not completely fixed, by #8456. This includes some small changes to ORM context that are a prerequisite for getting ORM adaptation to be better. Have these in 2.0.0b4 so that we have at least a better starting point. References: #8168 Change-Id: I51dbe333b156048836d074fbba1d850f9eb67fd2
* | changelog updatesMike Bayer2022-12-0511-40/+55
| | | | | | | | | | | | | | prep for 2.0.0b4 Change-Id: I2bf7249f6ed0c120b9d04d81eaecdf8593729c83 (cherry picked from commit 42876aabb5f893e1922676eb809e6b37c0519ed8)
* | rename some GitHub actions to use test names as prefix, as introduced in ↵Jonathan Vanasco2022-12-052-3/+3
| | | | | | | | | | rel_1_4 (#8933) Change-Id: I7f3aa96447ade605becbdef01bc19f3b78dbd6d1
* | Merge "Add compatibility properties to Range; implement pep-484" into mainmike bayer2022-12-052-82/+182
|\ \ | |/ |/|
| * Add compatibility properties to Range; implement pep-484Lele Gaifax2022-12-052-82/+182
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a bunch of properties to new PG Range class for compatibility with other implementations, providing a more similar API to access emptiness and bounds status. The naming conventions here derive from PostgreSQL itself, see https://www.postgresql.org/docs/9.3/functions-range.html . pep-484 also implemented by Mike, as this is a pretty type-intensive module. Co-authored-by: Mike Bayer <mike_mp@zzzcomputing.com> Closes: #8927 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8927 Pull-request-sha: 8b9e7b7e3345673b43aeabd7ec88b88dc3cfa7eb Change-Id: I0b1d49311517ee1cc1377a974ed0a860ea5756e4
* | Merge "Rewrite positional handling, test for "numeric"" into mainmike bayer2022-12-0528-348/+989
|\ \
| * | Rewrite positional handling, test for "numeric"Federico Caselli2022-12-0528-348/+989
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changed how the positional compilation is performed. It's rendered by the compiler the same as the pyformat compilation. The string is then processed to replace the placeholders with the correct ones, and to obtain the correct order of the parameters. This vastly simplifies the computation of the order of the parameters, that in case of nested CTE is very hard to compute correctly. Reworked how numeric paramstyle behavers: - added support for repeated parameter, without duplicating them like in normal positional dialects - implement insertmany support. This requires that the dialect supports out of order placehoders, since all parameters that are not part of the VALUES clauses are placed at the beginning of the parameter tuple - support for different identifiers for a numeric parameter. It's for example possible to use postgresql style placeholder $1, $2, etc Added two new dialect based on sqlite to test "numeric" fully using both :1 style and $1 style. Includes a workaround for SQLite's not-really-correct numeric implementation. Changed parmstyle of asyncpg dialect to use numeric, rendering with its native $ identifiers Fixes: #8926 Fixes: #8849 Change-Id: I7c640467d49adfe6d795cc84296fc7403dcad4d6
* | Type annotations for sqlalchemy.ext.automapGleb Kisenkov2022-12-053-62/+244
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An attempt to annotate `lib/sqlalchemy/ext/automap.py` with type hints (issue [#6810](https://github.com/sqlalchemy/sqlalchemy/issues/6810#issuecomment-1127062951)). More info on how I approach it could be found in [the earlier PR](https://github.com/sqlalchemy/sqlalchemy/pull/8775). This pull request is: - [ ] A documentation / typographical error fix - Good to go, no issue or tests are needed - [ ] A short code fix - please include the issue number, and create an issue if none exists, which must include a complete example of the issue. one line code fixes without an issue and demonstration will not be accepted. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. one line code fixes without tests will not be accepted. - [x] A new feature implementation - please include the issue number, and create an issue if none exists, which must include a complete example of how the feature would look. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. **Have a nice day!** Closes: #8874 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8874 Pull-request-sha: 834d58d77c2cfd09ea874f01eb7b75a2ea0db7cd Change-Id: Ie64b2be7a51ddc83ef8f23385fb63db5b5c1bc17
* Merge "adjustments for unreliable gc" into mainmike bayer2022-12-055-39/+60
|\
| * adjustments for unreliable gcMike Bayer2022-12-045-39/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | sporadic (and at the moment persistent) test failures related to aiosqlite seem to have in common that Python gc stops working fully when we run a lot of tests with aiosqlite. The failures are not limited to aiosqlite as they are more involving places where we assume or expect gc.collect() to get rid of things, and it doesn't. Identify (based on reproducible case on the d3 CI runner) the spots where this happens and add fixes. test/orm/test_transaction.py test_gced_delete_on_rollback has always been a very sensitive test with a lot of issues, so here we move it to the test_memusage suite and limit it only to when the memusage suite is running. Change-Id: I683412d0effe8732c45980b40722e5bb63431177
* | Merge "Fixed an invalid syntax in an except statement" into mainmike bayer2022-12-051-1/+1
|\ \
| * | Fixed an invalid syntax in an except statementwiseaidev2022-12-051-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ### Description As the title suggests, I have fixed an invalid syntax in the docs for an `except` statement while reading the unusual. ### Checklist <!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once) --> This pull request is: - [x] A documentation / typographical error fix - Good to go, no issue or tests are needed - [ ] A short code fix - please include the issue number, and create an issue if none exists, which must include a complete example of the issue. one line code fixes without an issue and demonstration will not be accepted. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. one line code fixes without tests will not be accepted. - [ ] A new feature implementation - please include the issue number, and create an issue if none exists, which must include a complete example of how the feature would look. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. **Have a nice day!** Closes: #8715 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8715 Pull-request-sha: e8be2bc4a5401ab2a5a0fc1d2e50d41fa437ae80 Change-Id: If8512bf1853f7cdb1ae655f0945cd922fff6fbce
* | Merge "Fix grammar (whatsnew_20.rst)" into mainmike bayer2022-12-051-1/+1
|\ \
| * | Fix grammar (whatsnew_20.rst)Sam Bull2022-12-051-1/+1
| |/ | | | | | | | | | | | | | | | | | | None Closes: #8835 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8835 Pull-request-sha: 7488c752d90ce305076ba06b7a4077dc67c0ea66 Change-Id: Iad959dcff21bd1aa593793c4a38cb795529468e8
* | doc change - Add new external dialect for openGaussj003562872022-12-051-0/+3
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <!-- Provide a general summary of your proposed changes in the Title field above --> ### Description <!-- Describe your changes in detail --> Added new external dialect for [openGauss](https://www.opengauss.org/en/). ### Checklist <!-- go over following points. check them with an `x` if they do apply, (they turn into clickable checkboxes once the PR is submitted, so no need to do everything at once) --> This pull request is: - [x] A documentation / typographical error fix - Good to go, no issue or tests are needed - [ ] A short code fix - please include the issue number, and create an issue if none exists, which must include a complete example of the issue. one line code fixes without an issue and demonstration will not be accepted. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. one line code fixes without tests will not be accepted. - [ ] A new feature implementation - please include the issue number, and create an issue if none exists, which must include a complete example of how the feature would look. - Please include: `Fixes: #<issue number>` in the commit message - please include tests. **Have a nice day!** Closes: #8803 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8803 Pull-request-sha: ca5a7f1310b2ce93ce33618e0609abe23b41a3da Change-Id: Ia8ca38f98f346fa3cc910ceb7af47f8c903eb587
* Merge "disallow same-named columns, unchecked replacement in Table" into mainmike bayer2022-12-0411-73/+419
|\
| * disallow same-named columns, unchecked replacement in TableMike Bayer2022-12-0411-73/+419
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed issue where table reflection using :paramref:`.Table.extend_existing` would fail to deduplicate a same-named column if the existing :class:`.Table` used a separate key. The :paramref:`.Table.autoload_replace` parameter would allow the column to be skipped but under no circumstances should a :class:`.Table` ever have the same-named column twice. Additionally, changed deprecation warnings to exceptions as were implemented in I1d58c8ebe081079cb669e7ead60886ffc1b1a7f5 . Fixes: #8925 Change-Id: I83d0f8658177a7ffbb06e01dbca91377d1a98d49
* | Merge "Order_by and group_by accept labels" into mainmike bayer2022-12-046-12/+62
|\ \
| * | Order_by and group_by accept labelsFederico Caselli2022-12-036-12/+62
| |/ | | | | | | | | | | Improve typing to accept labels in ordey_by mand group_by. Change-Id: I33e5d6f64633d39a220108d412ef84d6478b25e6
* | Some test pipeline updatesFederico Caselli2022-12-031-16/+18
|/ | | | | | Add back pypy, python 3.12 Change-Id: Ie3b3b890d75b3939b3d5f684ec7eadadfe06a5ea
* add spaces, leading underscore to oracle checksMike Bayer2022-12-023-7/+76
| | | | | | | | | | | | Expand the test suite from #8708 which unfortunately did not exercise the bound parameter codepaths completely. Continued fixes for Oracle fix :ticket:`8708` released in 1.4.43 where bound parameter names that start with underscores, which are disallowed by Oracle, were still not being properly escaped in all circumstances. Fixes: #8708 Change-Id: Ic389c09bd7c53b773e5de35f1a18ef20769b92a7
* add backports for 2.0/ 1.4 changesMike Bayer2022-12-0214-9/+41
| | | | Change-Id: I5aab8b25337f67385fc998954ab1fa883c175cc2
* Merge "Fix positional compiling bugs" into mainmike bayer2022-12-0212-97/+572
|\
| * Fix positional compiling bugsFederico Caselli2022-12-0112-97/+572
| | | | | | | | | | | | | | | | | | | | | | Fixed a series of issues regarding positionally rendered bound parameters, such as those used for SQLite, asyncpg, MySQL and others. Some compiled forms would not maintain the order of parameters correctly, such as the PostgreSQL ``regexp_replace()`` function as well as within the "nesting" feature of the :class:`.CTE` construct first introduced in :ticket:`4123`. Fixes: #8827 Change-Id: I9813ed7c358cc5c1e26725c48df546b209a442cb
* | Merge "disable setinputsizes only for true DBAPI executemany" into mainmike bayer2022-12-023-62/+90
|\ \
| * | disable setinputsizes only for true DBAPI executemanyMike Bayer2022-12-013-62/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed regression caused by the combination of :ticket:`8177`, re-enable setinputsizes for SQL server unless fast_executemany + DBAPI executemany is used for a statement, along with :ticket:`6047`, implement "insertmanyvalues", which bypasses DBAPI executemany in place of a custom DBAPI execute for INSERT statements. setinputsizes would incorrectly not be used for a multiple parameter-set INSERT statement that used "insertmanyvalues" if fast_executemany were turned on, as the check would incorrectly assume this is a DBAPI executemany call. The "regression" would then be that the "insertmanyvalues" statement format is apparently slightly more sensitive to multiple rows that don't use the same types for each row, so in such a case setinputsizes is especially needed. The fix repairs the fast_executemany check so that it only disables setinputsizes if true DBAPI executemany is to be used. Fixes: #8917 Change-Id: I78895606a99848d4f92ecf38ded92dc5d6d48c6f
* | | Merge "add new pattern for single inh column override" into mainmike bayer2022-12-0110-117/+294
|\ \ \ | |/ / |/| |
| * | add new pattern for single inh column overrideMike Bayer2022-11-3010-117/+294
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added a new parameter :paramref:`_orm.mapped_column.use_existing_column` to accommodate the use case of a single-table inheritance mapping that uses the pattern of more than one subclass indicating the same column to take place on the superclass. This pattern was previously possible by using :func:`_orm.declared_attr` in conjunction with locating the existing column in the ``.__table__`` of the superclass, however is now updated to work with :func:`_orm.mapped_column` as well as with pep-484 typing, in a simple and succinct way. Fixes: #8822 Change-Id: I2296a4a775da976c642c86567852cdc792610eaf
* | | get aiosqlite to run on python 3 but not 3.11, attempt 2Mike Bayer2022-11-301-11/+5
| | | | | | | | | | | | Change-Id: Iee0077f8c662da59ee63fa73296cb04ab1b09551
* | | use python 3.11 current, dont use aiosqlite on py311Mike Bayer2022-11-301-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Py 3.11 is released so I assume we can remove "rc" qualifiers here aiosqlite is causing python 3.11 crashes, so I assume this is due to https://github.com/python/cpython/issues/99205. I'm only guessing the syntax here, so there may be subsequent commits if this doesnt work Change-Id: I6f2ead3e0aca933a972efadf3891edbcdd83501c
* | | Merge "[sqlite] Reflect DEFERRABLE and INITIALLY options for foreign keys" ↵mike bayer2022-11-303-1/+77
|\ \ \ | | | | | | | | | | | | into main
| * | | [sqlite] Reflect DEFERRABLE and INITIALLY options for foreign keysMichael Gorven2022-11-303-1/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added support for the SQLite backend to reflect the "DEFERRABLE" and "INITIALLY" keywords which may be present on a foreign key construct. Pull request courtesy Michael Gorven. Fixes: #8903 Closes: #8904 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8904 Pull-request-sha: 52aa4cf77482c4051899e21bea75b9830e4c3efa Change-Id: I713906db1a458d8f1be39625841ca3bbc03ec835
* | | | Add "compare" on dataclass fieldsSimon Schiele2022-11-305-25/+100
| |_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added :paramref:`_orm.mapped_column.compare` parameter to relevant ORM attribute constructs including :func:`_orm.mapped_column`, :func:`_orm.relationship` etc. to provide for the Python dataclasses ``compare`` parameter on ``field()``, when using the :ref:`orm_declarative_native_dataclasses` feature. Pull request courtesy Simon Schiele. Added an additional case for associationproxy into test_dc_transforms.py -> test_attribute_options Fixes: #8905 Closes: #8906 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8906 Pull-request-sha: ea9a53d2ca60befdd0c570013c0e57a78c11dd4a Change-Id: I390d043b06c1d668242325ef86e2f7b7dbfac442
* | | Merge "Improve support for enum in mapped classes" into mainmike bayer2022-11-3010-10/+666
|\ \ \ | |_|/ |/| |
| * | Improve support for enum in mapped classesFederico Caselli2022-11-2910-10/+666
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a new system by which TypeEngine objects have some say in how the declarative type registry interprets them. The Enum datatype is the primary target for this but it is hoped the system may be useful for other types as well. Fixes: #8859 Change-Id: I15ac3daee770408b5795746f47c1bbd931b7d26d
* | | Merge "annotated / DC forms for association proxy" into mainmike bayer2022-11-3013-312/+800
|\ \ \ | |_|/ |/| |
| * | annotated / DC forms for association proxyMike Bayer2022-11-2913-312/+800
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added support for the :func:`.association_proxy` extension function to take part within Python ``dataclasses`` configuration, when using the native dataclasses feature described at :ref:`orm_declarative_native_dataclasses`. Included are attribute-level arguments including :paramref:`.association_proxy.init` and :paramref:`.association_proxy.default_factory`. Documentation for association proxy has also been updated to use "Annotated Declarative Table" forms within examples, including type annotations used for :class:`.AssocationProxy` itself. Also modernized documentation examples in sqlalchemy.ext.mutable, which was not up to date even for 1.4 style code. Corrected typing for relationship(secondary) where "secondary" accepts a callable (i.e. lambda) as well Fixes: #8878 Fixes: #8876 Fixes: #8880 Change-Id: Ibd4f3591155a89f915713393e103e61cc072ed57
* | Merge "Add value-level hooks for SQL type detection; apply to Range" into mainmike bayer2022-11-295-0/+94
|\ \ | |/ |/|
| * Add value-level hooks for SQL type detection; apply to RangeLele Gaifax2022-11-295-0/+94
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added additional type-detection for the new PostgreSQL :class:`_postgresql.Range` type, where previous cases that allowed the psycopg2-native range objects to be received directly by the DBAPI without SQLAlchemy intercepting them stopped working, as we now have our own value object. The :class:`_postgresql.Range` object has been enhanced such that SQLAlchemy Core detects it in otherwise ambiguous situations (such as comparison to dates) and applies appropriate bind handlers. Pull request courtesy Lele Gaifax. Fixes: #8884 Closes: #8886 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/8886 Pull-request-sha: 6e95e08a30597d3735ab38f2f1a2ccabd968852c Change-Id: I3ca277c826dcf4b5644f44eb251345b439a84ee4
* | update for mypy 1.0 devFederico Caselli2022-11-2910-19/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As I need dmypy to work without facing [1], I am running the latest build of mypy which seems so far to finally not have that issue. update constructs that latest mypy is being more picky about, including better typing for the _NONE_NAME symbol used in constraints (porting those elements from the Enum patch at I15ac3daee770408b5795746f47c1bbd931b7d26d) [1] https://github.com/python/mypy/issues/12744 Change-Id: Ib3f56787fa65ea9bb2e6a0bccc4d99f54c516dad
* | Add PyAthena Dialect (#8898)Jason Myers2022-11-291-0/+3
| | | | | | | | | | * Add PyAthena Dialect * Changing order
View Lorry Controller Status