summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* update stubs, move changelog to separate filetmpFederico Caselli2023-04-262-6/+6
| | | | Change-Id: I5ea33c4f7a35a57aab32e075e0b02b676cf03d79
* Changelog: add 1.10.5 (unreleased) entry note about docstring code formattingJames Addison2023-04-261-0/+6
|
* Merge "Improve typing." into mainmike bayer2023-04-251-0/+6
|\
| * Improve typing.Federico Caselli2023-04-131-0/+6
| | | | | | | | | | | | | | | | Correctly pass previously ignored arguments ``insert_before`` and ``insert_after`` in ``batch_alter_column`` Fixes: #1221 Change-Id: I79c9144f3e521fca00a0c32462ae2a69f9f7a032
* | add missing tag to 1.10.4 changelogFederico Caselli2023-04-241-1/+1
| | | | | | | | Change-Id: Ifbec22c07ce887f4e25d25ad47aff44dcbae366b
* | Version 1.10.5 placeholderMike Bayer2023-04-241-0/+4
| |
* | - 1.10.4rel_1_10_4Mike Bayer2023-04-244-18/+20
|/
* Merge "Use column sort in index compare on postgresql" into mainmike bayer2023-04-101-0/+6
|\
| * Use column sort in index compare on postgresqlCaselIT2023-04-101-0/+6
| | | | | | | | | | | | | | | | Added support for autogenerate comparison of indexes on PostgreSQL which include SQL sort option, such as ``ASC`` or ``NULLS FIRST``. Fixes: #1213 Change-Id: I3ddcb647928d948e41462b1c889b1cbb515ace4f
* | uniquify cols for FK table objectMike Bayer2023-04-071-0/+9
|/ | | | | | | | | | | Fixed issue where using a directive such as ``op.create_foreign_key()`` to create a self-referential constraint on a single table where the same column were present on both sides (e.g. within a composite foreign key) would produce an error under SQLAlchemy 2.0 and a warning under SQLAlchemy 1.4 indicating that a duplicate column were being added to a table. Change-Id: I2a8f5d8def2714792bffcdfb8bf88a5080ec8ce7 Fixes: #1215
* Version 1.10.4 placeholderMike Bayer2023-04-051-0/+4
|
* - 1.10.3rel_1_10_3Mike Bayer2023-04-054-16/+18
|
* Fix issues in autogenerate of function index removalCaselIT2023-04-041-0/+6
| | | | | | | | Fixed error raised by alembic when running autogenerate after removing a function based index. Fixes: #1212 Change-Id: Idc565d661229afda89d44e36786bb0357323e604
* Add docs for data migrationsVlastimil Zíma2023-04-021-0/+43
| | | | | | | | | | | | | | | | | | | | | | | ### Description I added a small docs regarding data migrations, based on #972. ### 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 **Have a nice day!** Closes: #1040 Pull-request: https://github.com/sqlalchemy/alembic/pull/1040 Pull-request-sha: c985e0d8096e750df35aa07dde71f432a57656b6 Change-Id: Icf6fdb1089eb7c386dad4401b99caaddc352d92f
* Fix unknown types reported by pyrightCaselIT2023-03-101-0/+7
| | | | | | | | | | Fixed various typing issues observed with pyright, including issues involving the combination of :class:`.Function` and :meth:`.MigrationContext.begin_transaction`. Fixes: #1191 Fixes: #1201 Change-Id: I9856a8f59c22130c8bbcbed3e19cf2e8a8bf0608
* Version 1.10.3 placeholderMike Bayer2023-03-081-0/+4
|
* - 1.10.2rel_1_10_2Mike Bayer2023-03-083-10/+11
|
* mock _NONE_NAME for < 1.3.24Mike Bayer2023-03-071-0/+7
| | | | | | | | | Fixed regression where Alembic would not run with older SQLAlchemy 1.3 versions prior to 1.3.24 due to a missing symbol. Workarounds have been applied for older 1.3 versions. Change-Id: Ie7b5f6295e55276f0e912bf2b10b8c96dad171b9 Fixes: #1196
* Version 1.10.2 placeholderMike Bayer2023-03-061-0/+4
|
* - 1.10.1rel_1_10_1Mike Bayer2023-03-064-20/+22
|
* Merge "improve autogen rendering for PG ExcludeConstraint" into mainmike bayer2023-03-071-0/+10
|\
| * improve autogen rendering for PG ExcludeConstraintJan Katins2023-03-061-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed issue regarding PostgreSQL :class:`.ExcludeConstraint`, where constraint elements which made use of :func:`.literal_column` could not be rendered for autogenerate. Additionally, using SQLAlchemy 2.0.5 or greater, :func:`.text()` constructs are also supported within PostgreSQL :class:`.ExcludeConstraint` objects for autogenerate render. Pull request courtesy Jan Katins. Fixes: #1184 Closes: #1185 Pull-request: https://github.com/sqlalchemy/alembic/pull/1185 Pull-request-sha: 68360ce9aa746a85407c5e1e04b8021123d98504 Change-Id: I302f3f4007a186ffac13b344ff6769dd302f28f5
* | distinguish between string contraint name and definedMike Bayer2023-03-061-0/+7
|/ | | | | | | | | | | | | | Take _NONE_NAME into account as a valid constraint name and don't skip these constraints or consider them to be unnamed. Thanks to typing this also revealed that previous batch versions were also keying "_NONE_NAME" constraints as though they were named. Fixed regression for 1.10.0 where :class:`.Constraint` objects were suddenly required to have non-None name fields when using batch mode, which was not previously a requirement. Change-Id: If4a7191a00848b19cb124bc6da362f3bc6ce1472 Fixes: #1195
* Version 1.10.1 placeholderMike Bayer2023-03-051-0/+4
|
* - 1.10.0rel_1_10_0Mike Bayer2023-03-057-48/+53
|
* changelog updatesMike Bayer2023-03-052-10/+13
| | | | Change-Id: I2c796e4120a4674a46f4ebedbf63d9e40ebe49b9
* Update example to sqlalchemy 2 (#1171)Sam Bull2023-03-011-3/+3
|
* Merge "Improved support for expression indexes" into mainmike bayer2023-03-013-0/+26
|\
| * Improved support for expression indexesCaselIT2023-02-263-0/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added support for autogenerate comparison of indexes on PostgreSQL which include SQL expressions; the previous warning that such indexes were skipped is now removed. This functionality requires SQLAlchemy 2.0. For older SQLAlchemy versions, these indexes are still skipped. Fixed issue where indexes on SQLite which include SQL expressions would not compare against themselves correctly, generating false positives. SQLAlchemy as of version 2 has no support for reflecting expression based indexes on SQLite; so for now, the behavior is that SQLite expression-based indexes are ignored for autogenerate compare, in the same way that PostgreSQL expression-based indexes were ignored for the time that SQLAlchemy did not support reflection of such indexes (which is now supported in SQLAlchemy 2.0 as well as this release of Alembic). Fixed issue in index detection where autogenerate change detection would consider indexes with the same columns but with different order as equal, while in general they are not equivalent in how a database will use them. Fixes: #1165 Fixes: #1166 Change-Id: I226408eed855b923172e5df0bdab005ed2cc9f53
* | Merge "add recursive_version_locations option for searching revision files" ↵mike bayer2023-03-012-0/+18
|\ \ | | | | | | | | | into main
| * | add recursive_version_locations option for searching revision filesostr000002023-02-282-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recursive traversal of revision files in a particular revision directory is now supported, by indicating ``recursive_version_locations = true`` in alembic.ini. Pull request courtesy ostr00000. Fixes: #760 Closes: #1182 Pull-request: https://github.com/sqlalchemy/alembic/pull/1182 Pull-request-sha: ecb0da48b459abd3f5e95390ec7030a7e3fcbc6d Change-Id: I711ca2dbd35fb9a2acdbfd374bcac13043b0d129
* | | Merge "set next version at 1.10.0" into mainmike bayer2023-03-011-1/+1
|\ \ \ | | |/ | |/|
| * | set next version at 1.10.0Mike Bayer2023-02-251-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | Will rebase current 1.10 gerrits to this one until we are very close to 1.10 issues being very close to ready for release. In the interim, I'd rather not have an 0.9 branch for emergency bugfixes. We are mostly here waiting on I226408eed855b923172e5df0bdab005ed2cc9f53 for 1.10 to be close to release. Change-Id: I9b568a19d6653ed54069b84187dcb10ad4150274
* | Escape sql server constriant namesCaselIT2023-02-281-0/+8
|/ | | | | | | | | Properly escape constraint name on SQL Server when dropping a column while specifying ``mssql_drop_default=True`` or ``mssql_drop_check=True`` or ``mssql_drop_foreign_key=True``. Fixes: #1187 Change-Id: I060442bc63c4e53f64724985e20e6e15e4335b6b
* Version 1.9.5 placeholderMike Bayer2023-02-161-0/+4
|
* - 1.9.4rel_1_9_4Mike Bayer2023-02-165-40/+43
|
* Merge "dont use server_default render_item for SQL compare" into mainmike bayer2023-02-161-0/+9
|\
| * dont use server_default render_item for SQL compareMike Bayer2023-02-151-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | Removed a mis-use of the :paramref:`.EnvironmentContext.configure.render_item` callable where the "server_default" renderer would be erroneously used within the server default comparison process, which is working against SQL expressions, not Python code. Change-Id: Id6fad1e6f5ac0a68bbd0e6b7e6088e451bf6dc2b References: #641 Fixes: #1180
* | Merge "collapse all chars for mssql defaults, move quoting" into mainmike bayer2023-02-161-0/+21
|\ \ | |/
| * collapse all chars for mssql defaults, move quotingMike Bayer2023-02-151-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ongoing fixes for SQL Server server default comparisons under autogenerate, adjusting for SQL Server's collapsing of whitespace between SQL function arguments when reporting on a function-based server default, as well as its arbitrary addition of parenthesis within arguments; the approach has now been made more aggressive by stripping the two default strings to compare of all whitespace, parenthesis, and quoting characters. Fixed PostgreSQL server default comparison to handle SQL expressions sent as ``text()`` constructs, such as ``text("substring('name', 1, 3)")``, which previously would raise errors when attempting to run a server-based comparison. Change-Id: Icd861f62653fc7b3900164c0d047821125e1305e Fixes: #1177
* | Merge "restore config object to merge command" into mainmike bayer2023-02-151-0/+7
|\ \
| * | restore config object to merge commandBrendan Gann2023-02-141-0/+7
| |/ | | | | | | | | | | | | | | | | | | | | | | | | Fixed regression introduced in 1.7.0 where the "config" object passed to the template context when running the :func:`.merge` command programmatically failed to be correctly populated. Pull request courtesy Brendan Gann. Closes: #1176 Pull-request: https://github.com/sqlalchemy/alembic/pull/1176 Pull-request-sha: cf6a886915f6bef6eeef8041804e316038955402 Change-Id: Idbab2dc0339cce6f8827d2f49156791600a82c1a
* | Follow up Ia98c8f9a93953f049378f5029e355a3f249ed638CaselIT2023-02-141-38/+8
|/ | | | | | that was merged prematurely Change-Id: I131dfb8dabf10457954f5216b1abadc976aebd38
* Include missing part of env.pySam Bull2023-02-131-12/+12
| | | | | | | | | | | This part is missing from the example, and if a user started with the async template, then they would have an `asyncio.run()` call in here, which breaks the script. Fixes: #1174 Closes: #1172 Pull-request: https://github.com/sqlalchemy/alembic/pull/1172 Pull-request-sha: fa2c55319d09fab4e1435433fa2d7e5fca5dc820 Change-Id: Ia98c8f9a93953f049378f5029e355a3f249ed638
* pin sphinx-copybutton and change configMike Bayer2023-02-092-1/+5
| | | | | | | | | | | | | | sphinx-copybutton introduced a new feature in 0.5.1 which includes a default configuration that breaks the regexp prompt matching scheme. set copybutton_exclude to not include ".gp" as that's the class where we exactly look for the prompts we are matching. pin sphinx-copybutton at 0.5.1 to avoid future problems. Change-Id: Ie03bc27a9190e71b63fc68b484f23e53b8cb72dc References: https://github.com/executablebooks/sphinx-copybutton/issues/185
* Version 1.9.4 placeholderMike Bayer2023-02-071-0/+4
|
* - 1.9.3rel_1_9_3Mike Bayer2023-02-073-11/+12
|
* add variant render step for user-defined typesMike Bayer2023-02-071-0/+8
| | | | | | | | | | | | | due to SQLA 2.0's variant being integrated into types, the variant rendering conditional would no longer take effect as the type was not under the "sqlalchemy" module namespace. Fixed issue where rendering of user-defined types that then went onto use the ``.with_variant()`` method would fail to render, if using SQLAlchemy 2.0's version of variants. Change-Id: I3c6f14325d6dffb2ddc1bf955753ee5a2de2cedd Fixes: #1167
* Version 1.9.3 placeholderMike Bayer2023-01-141-0/+4
|
* - 1.9.2rel_1_9_2Mike Bayer2023-01-144-18/+20
|
View Lorry Controller Status