mirror of
https://github.com/sqlalchemy/sqlalchemy.git
synced 2026-05-06 08:56:51 -04:00
Move links etc. to github, new alembic links
Change-Id: I59392d355a216ae59552a04c5508f548b901aa7b (cherry picked from commit50417cf758) (cherry picked from commitd04575c554) (cherry picked from commitfcb4c96cd8)
This commit is contained in:
+1
-1
@@ -1,4 +1,4 @@
|
||||
[gerrit]
|
||||
host=gerrit.sqlalchemy.org
|
||||
project=zzzeek/sqlalchemy
|
||||
project=sqlalchemy/sqlalchemy
|
||||
defaultbranch=rel_1_0
|
||||
|
||||
Vendored
-12
@@ -127,7 +127,6 @@
|
||||
.. change::
|
||||
:tags: bug, ext
|
||||
:versions: 0.9.5, 1.0.0b1
|
||||
:pullreq: bitbucket:24
|
||||
:tickets: 3093, 3051
|
||||
|
||||
Fixed bug where :meth:`.MutableDict.setdefault` didn't return the
|
||||
@@ -137,7 +136,6 @@
|
||||
.. change::
|
||||
:tags: bug, mysql
|
||||
:versions: 0.9.5, 1.0.0b1
|
||||
:pullreq: bitbucket:15
|
||||
|
||||
Added support for reflecting tables where an index includes
|
||||
KEY_BLOCK_SIZE using an equal sign. Pull request courtesy
|
||||
@@ -165,7 +163,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, postgresql
|
||||
:pullreq: bitbucket:13
|
||||
:versions: 0.9.5, 1.0.0b1
|
||||
|
||||
Added a new "disconnect" message "connection has been closed unexpectedly".
|
||||
@@ -311,7 +308,6 @@
|
||||
:tags: bug, mysql
|
||||
:versions: 0.9.3
|
||||
:tickets: 2966
|
||||
:pullreq: bitbucket:12
|
||||
|
||||
Added support for the ``PARTITION BY`` and ``PARTITIONS``
|
||||
MySQL table keywords, specified as ``mysql_partition_by='value'`` and
|
||||
@@ -339,7 +335,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, sqlite
|
||||
:pullreq: github:72
|
||||
|
||||
Restored a change that was missed in the backport of unique
|
||||
constraint reflection to 0.8, where :class:`.UniqueConstraint`
|
||||
@@ -392,7 +387,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, mysql
|
||||
:pullreq: github:61
|
||||
:versions: 0.9.2
|
||||
|
||||
Some missing methods added to the cymysql dialect, including
|
||||
@@ -401,7 +395,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, py3k
|
||||
:pullreq: github:63
|
||||
|
||||
Fixed Py3K bug where a missing import would cause "literal binary"
|
||||
mode to fail to import "util.binary_type" when rendering a bound
|
||||
@@ -411,7 +404,6 @@
|
||||
.. change::
|
||||
:tags: bug, orm
|
||||
:versions: 0.9.2
|
||||
:pullreq: github:58
|
||||
|
||||
Fixed error message when an iterator object is passed to
|
||||
:func:`.class_mapper` or similar, where the error would fail to
|
||||
@@ -444,7 +436,6 @@
|
||||
.. change::
|
||||
:tags: bug, mssql, pymssql
|
||||
:versions: 0.9.0
|
||||
:pullreq: github:51
|
||||
|
||||
Added "Net-Lib error during Connection reset by peer" message
|
||||
to the list of messages checked for "disconnect" within the
|
||||
@@ -571,7 +562,6 @@
|
||||
.. change::
|
||||
:tags: bug, mssql
|
||||
:versions: 0.9.0
|
||||
:pullreq: bitbucket:7
|
||||
|
||||
Fixed bug introduced in 0.8.0 where the ``DROP INDEX``
|
||||
statement for an index in MSSQL would render incorrectly if the
|
||||
@@ -1202,7 +1192,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, engine
|
||||
:pullreq: github:6
|
||||
:versions: 0.9.0b1
|
||||
|
||||
Fixed bug where the ``reset_on_return`` argument to various :class:`.Pool`
|
||||
@@ -1334,7 +1323,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, postgresql
|
||||
:pullreq: github:2
|
||||
:tickets: 2735
|
||||
|
||||
Fixed the HSTORE type to correctly encode/decode for unicode.
|
||||
|
||||
Vendored
-37
@@ -155,7 +155,6 @@
|
||||
.. change::
|
||||
:tags: bug, py3k, mysql
|
||||
:tickets: 3333
|
||||
:pullreq: github:158
|
||||
:versions: 1.0.0b2
|
||||
|
||||
Fixed the :class:`.mysql.BIT` type on Py3K which was not using the
|
||||
@@ -190,7 +189,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:pullreq: bitbucket:45
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Added support for the ``CONCURRENTLY`` keyword with Postgresql
|
||||
@@ -203,7 +201,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, ext, py3k
|
||||
:pullreq: github:154
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Fixed bug where the association proxy list class would not interpret
|
||||
@@ -212,7 +209,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, sqlite
|
||||
:pullreq: bitbucket:42
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Added support for partial indexes (e.g. with a WHERE clause) on
|
||||
@@ -248,7 +244,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, orm
|
||||
:pullreq: github:147
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Fixed bug where TypeError raised when :meth:`.Query.join` called
|
||||
@@ -321,7 +316,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, postgresql
|
||||
:pullreq: github:145
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Added support for the :class:`postgresql.JSONB` datatype when
|
||||
@@ -397,7 +391,6 @@
|
||||
.. change::
|
||||
:tags: bug, sql
|
||||
:versions: 1.0.0b1
|
||||
:pullreq: bitbucket:41
|
||||
|
||||
Added the ``native_enum`` flag to the ``__repr__()`` output
|
||||
of :class:`.Enum`, which is mostly important when using it with
|
||||
@@ -715,7 +708,6 @@
|
||||
.. change::
|
||||
:tags: bug, ext
|
||||
:versions: 1.0.0b1
|
||||
:pullrequest: bitbucket:28
|
||||
|
||||
Fixed bug where :class:`.ext.mutable.MutableDict`
|
||||
failed to implement the ``update()`` dictionary method, thus
|
||||
@@ -724,7 +716,6 @@
|
||||
.. change::
|
||||
:tags: bug, ext
|
||||
:versions: 1.0.0b1
|
||||
:pullrequest: bitbucket:27
|
||||
|
||||
Fixed bug where a custom subclass of :class:`.ext.mutable.MutableDict`
|
||||
would not show up in a "coerce" operation, and would instead
|
||||
@@ -745,7 +736,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql, pg8000
|
||||
:versions: 1.0.0b1
|
||||
:pullreq: github:125
|
||||
|
||||
Support is added for "sane multi row count" with the pg8000 driver,
|
||||
which applies mostly to when using versioning with the ORM.
|
||||
@@ -816,7 +806,6 @@
|
||||
:tags: bug, postgresql
|
||||
:versions: 1.0.0b1
|
||||
:tickets: 3141
|
||||
:pullreq: github:124
|
||||
|
||||
Fixed bug in :class:`.postgresql.array` object where comparison
|
||||
to a plain Python list would fail to use the correct array constructor.
|
||||
@@ -976,7 +965,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:versions: 1.0.0b1
|
||||
:pullreq: bitbucket:22
|
||||
:tickets: 3078
|
||||
|
||||
Added kw argument ``postgresql_regconfig`` to the
|
||||
@@ -987,14 +975,12 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:versions: 1.0.0b1
|
||||
:pullreq: github:101
|
||||
|
||||
Added support for Postgresql JSONB via :class:`.JSONB`. Pull request
|
||||
courtesy Damian Dimmich.
|
||||
|
||||
.. change::
|
||||
:tags: feature, mssql
|
||||
:pullreq: github:98
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Enabled "multivalues insert" for SQL Server 2008. Pull request
|
||||
@@ -1123,7 +1109,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, examples
|
||||
:pullreq: bitbucket:21
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Added a new example illustrating materialized paths, using the
|
||||
@@ -1131,7 +1116,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, testsuite
|
||||
:pullreq: github:95
|
||||
:versions: 1.0.0b1
|
||||
|
||||
In public test suite, shanged to use of ``String(40)`` from
|
||||
@@ -1155,7 +1139,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:versions: 1.0.0b1
|
||||
:pullreq: github:88
|
||||
|
||||
Added support for AUTOCOMMIT isolation level when using the pg8000
|
||||
DBAPI. Pull request courtesy Tony Locke.
|
||||
@@ -1164,7 +1147,6 @@
|
||||
:tags: bug, postgresql
|
||||
:tickets: 3021
|
||||
:versions: 1.0.0b1
|
||||
:pullreq: github:87
|
||||
|
||||
The psycopg2 ``.closed`` accessor is now consulted when determining
|
||||
if an exception is a "disconnect" error; ideally, this should remove
|
||||
@@ -1227,7 +1209,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:tickets: 2785
|
||||
:pullreq: bitbucket:18
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Added a new flag :paramref:`.ARRAY.zero_indexes` to the Postgresql
|
||||
@@ -1319,7 +1300,6 @@
|
||||
.. change::
|
||||
:tags: bug, py3k, tests
|
||||
:tickets: 2830
|
||||
:pullreq: bitbucket:2830
|
||||
:versions: 1.0.0b1
|
||||
|
||||
Corrected for some deprecation warnings involving the ``imp``
|
||||
@@ -1506,7 +1486,6 @@
|
||||
.. change::
|
||||
:tags: bug, sql
|
||||
:tickets: 2988
|
||||
:pullreq: github:78
|
||||
|
||||
Fixed an 0.9 regression where a :class:`.Table` that failed to
|
||||
reflect correctly wouldn't be removed from the parent
|
||||
@@ -1585,7 +1564,6 @@
|
||||
.. change::
|
||||
:tags: feature, oracle
|
||||
:tickets: 2911
|
||||
:pullreq: github:74
|
||||
|
||||
Added a new engine option ``coerce_to_unicode=True`` to the
|
||||
cx_Oracle dialect, which restores the cx_Oracle outputtypehandler
|
||||
@@ -1806,7 +1784,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: sqlite, bug
|
||||
:pullreq: github:65
|
||||
|
||||
Support has been added to SQLite type reflection to fully support
|
||||
the "type affinity" contract specified at http://www.sqlite.org/datatype3.html.
|
||||
@@ -1820,14 +1797,12 @@
|
||||
|
||||
.. change::
|
||||
:tags: postgresql, feature
|
||||
:pullreq: github:64
|
||||
|
||||
Added the :attr:`.TypeEngine.python_type` convenience accessor onto the
|
||||
:class:`.postgresql.ARRAY` type. Pull request courtesy Alexey Terentev.
|
||||
|
||||
.. change::
|
||||
:tags: examples, feature
|
||||
:pullreq: github:41
|
||||
|
||||
Added optional "changed" column to the versioned rows example, as well
|
||||
as support for when the versioned :class:`.Table` has an explicit
|
||||
@@ -1867,7 +1842,6 @@
|
||||
.. change::
|
||||
:tags: bug, mysql, cymysql
|
||||
:tickets: 2934
|
||||
:pullreq: github:69
|
||||
|
||||
Fixed bug in cymysql dialect where a version string such as
|
||||
``'33a-MariaDB'`` would fail to parse properly. Pull request
|
||||
@@ -1896,7 +1870,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, sql
|
||||
:pullreq: github:67
|
||||
|
||||
Fixed regression in new "naming convention" feature where conventions
|
||||
would fail if the referred table in a foreign key contained a schema
|
||||
@@ -2186,7 +2159,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, sql
|
||||
:pullreq: bitbucket:11
|
||||
|
||||
A :class:`.UniqueConstraint` created inline with a :class:`.Table`
|
||||
that has no columns within it will be skipped. Pullreq courtesy
|
||||
@@ -2194,7 +2166,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, mssql
|
||||
:pullreq: bitbucket:11
|
||||
|
||||
Added an option ``mssql_clustered`` to the :class:`.UniqueConstraint`
|
||||
and :class:`.PrimaryKeyConstraint` constructs; on SQL Server, this adds
|
||||
@@ -2336,7 +2307,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, py3k, cextensions
|
||||
:pullreq: github:55
|
||||
|
||||
Fixed an issue where the C extensions in Py3K are using the wrong API
|
||||
to specify the top-level module function, which breaks
|
||||
@@ -2347,7 +2317,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, schema
|
||||
:pullreq: github:57
|
||||
|
||||
Restored :class:`sqlalchemy.schema.SchemaVisitor` to the ``.schema``
|
||||
module. Pullreq courtesy Sean Dague.
|
||||
@@ -2416,7 +2385,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, orm
|
||||
:pullreq: bitbucket:9
|
||||
|
||||
Fixed bug where using new :attr:`.Session.info` attribute would fail
|
||||
if the ``.info`` argument were only passed to the :class:`.sessionmaker`
|
||||
@@ -2496,7 +2464,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:tickets: 2581
|
||||
:pullreq: github:50
|
||||
|
||||
Support for Postgresql JSON has been added, using the new
|
||||
:class:`.JSON` type. Huge thanks to Nathan Rice for
|
||||
@@ -2546,7 +2513,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:pullreq: bitbucket:8
|
||||
|
||||
Added support for Postgresql TSVECTOR via the
|
||||
:class:`.postgresql.TSVECTOR` type. Pull request courtesy
|
||||
@@ -2607,7 +2573,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, orm, collections, py3k
|
||||
:pullreq: github:40
|
||||
|
||||
Added support for the Python 3 method ``list.clear()`` within
|
||||
the ORM collection instrumentation system; pull request
|
||||
@@ -2650,7 +2615,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, sql
|
||||
:pullreq: github:42
|
||||
|
||||
A new API for specifying the ``FOR UPDATE`` clause of a ``SELECT``
|
||||
is added with the new :meth:`.GenerativeSelect.with_for_update` method.
|
||||
@@ -2667,7 +2631,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, orm
|
||||
:pullreq: github:42
|
||||
|
||||
A new API for specifying the ``FOR UPDATE`` clause of a ``SELECT``
|
||||
is added with the new :meth:`.Query.with_for_update` method,
|
||||
|
||||
Vendored
-40
@@ -498,7 +498,6 @@
|
||||
.. change::
|
||||
:tags: bug, sql
|
||||
:tickets: 3643
|
||||
:pullreq: github:232
|
||||
|
||||
Fixed issue where the "literal_binds" flag was not propagated
|
||||
for :func:`.expression.insert`, :func:`.expression.update` or
|
||||
@@ -570,7 +569,6 @@
|
||||
.. change::
|
||||
:tags: bug, mssql
|
||||
:tickets: 3624
|
||||
:pullreq: bitbucket:70
|
||||
|
||||
Fixed the syntax of the :func:`.extract` function when used on
|
||||
MSSQL against a datetime value; the quotes around the keyword
|
||||
@@ -612,7 +610,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, mysql
|
||||
:pullreq: github:222
|
||||
|
||||
Added new reserved words for MySQL 5.7 to the MySQL dialect,
|
||||
including 'generated', 'optimizer_costs', 'stored', 'virtual'.
|
||||
@@ -750,7 +747,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, postgresql
|
||||
:pullreq: github:216
|
||||
:tickets: 3573
|
||||
|
||||
|
||||
@@ -761,7 +757,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, postgresql
|
||||
:pullreq: github:215
|
||||
|
||||
|
||||
Fixed bug where some varieties of SQL expression passed to the
|
||||
@@ -770,7 +765,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, orm, declarative
|
||||
:pullreq: github:212
|
||||
|
||||
|
||||
Fixed bug where in Py2K a unicode literal would not be accepted as the
|
||||
@@ -780,7 +774,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, mssql
|
||||
:pullreq: github:206
|
||||
|
||||
A descriptive ValueError is now raised in the event that SQL server
|
||||
returns an invalid date or time format from a DATE or TIME
|
||||
@@ -789,7 +782,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, py3k
|
||||
:pullreq: github:210, github:218, github:211
|
||||
|
||||
Updates to internal getargspec() calls, some py36-related
|
||||
fixture updates, and alterations to two iterators to "return" instead
|
||||
@@ -810,7 +802,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, sql
|
||||
:pullreq: github:200
|
||||
|
||||
Added support for parameter-ordered SET clauses in an UPDATE
|
||||
statement. This feature is available by passing the
|
||||
@@ -873,7 +864,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, mssql
|
||||
:pullreq: github:213
|
||||
|
||||
|
||||
Fixed issue where DDL generated for the MSSQL types DATETIME2,
|
||||
@@ -919,7 +909,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, orm
|
||||
:pullreq: github:201
|
||||
|
||||
Added new method :meth:`.Query.one_or_none`; same as
|
||||
:meth:`.Query.one` but returns None if no row found. Pull request
|
||||
@@ -984,7 +973,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, postgresql
|
||||
:pullreq: github:190
|
||||
|
||||
|
||||
An adjustment to the new Postgresql feature of reflecting storage
|
||||
@@ -1018,7 +1006,6 @@
|
||||
.. change::
|
||||
:tags: feature, sql
|
||||
:tickets: 3459
|
||||
:pullreq: bitbucket:56
|
||||
|
||||
Added a :meth:`.ColumnElement.cast` method which performs the same
|
||||
purpose as the standalone :func:`.cast` function. Pull request
|
||||
@@ -1065,7 +1052,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, sql
|
||||
:pullreq: github:188
|
||||
|
||||
Fixed bug where the modulus SQL operator wouldn't work in reverse
|
||||
due to a missing ``__rmod__`` method. Pull request courtesy
|
||||
@@ -1073,7 +1059,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, schema
|
||||
:pullreq: github:186
|
||||
|
||||
Added support for the MINVALUE, MAXVALUE, NO MINVALUE, NO MAXVALUE,
|
||||
and CYCLE arguments for CREATE SEQUENCE as supported by Postgresql
|
||||
@@ -1168,7 +1153,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:tickets: 3455
|
||||
:pullreq: github:179
|
||||
|
||||
Added support for storage parameters under CREATE INDEX, using
|
||||
a new keyword argument ``postgresql_with``. Also added support for
|
||||
@@ -1203,7 +1187,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:pullreq: github:182
|
||||
|
||||
Added new execution option ``max_row_buffer`` which is interpreted
|
||||
by the psycopg2 dialect when the ``stream_results`` option is
|
||||
@@ -1215,7 +1198,6 @@
|
||||
.. change::
|
||||
:tags: bug, orm
|
||||
:tickets: 3451
|
||||
:pullreq: github:181
|
||||
|
||||
Fixed bug in new :meth:`.Session.bulk_update_mappings` feature where
|
||||
the primary key columns used in the WHERE clause to locate the row
|
||||
@@ -1280,7 +1262,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, ext
|
||||
:pullreq: bitbucket:54
|
||||
|
||||
Added support for ``*args`` to be passed to the baked query
|
||||
initial callable, in the same way that ``*args`` are supported
|
||||
@@ -1687,7 +1668,6 @@
|
||||
.. change::
|
||||
:tags: bug, firebird
|
||||
:tickets: 3380
|
||||
:pullreq: github:168
|
||||
|
||||
Fixed a regression due to :ticket:`3034` where limit/offset
|
||||
clauses were not properly interpreted by the Firebird dialect.
|
||||
@@ -1858,7 +1838,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, mssql
|
||||
:pullreq: github:166
|
||||
|
||||
Using the ``Binary`` constructor now present in pymssql rather than
|
||||
patching one in. Pull request courtesy Ramiro Morales.
|
||||
@@ -1876,7 +1855,6 @@
|
||||
.. change::
|
||||
:tags: feature, sql
|
||||
:tickets: 3084
|
||||
:pullreq: bitbucket:47
|
||||
|
||||
The topological sorting used to sort :class:`.Table` objects
|
||||
and available via the :attr:`.MetaData.sorted_tables` collection
|
||||
@@ -1894,7 +1872,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, orm
|
||||
:pullreq: github:164
|
||||
|
||||
Added new argument :paramref:`.Query.update.update_args` which allows
|
||||
kw arguments such as ``mysql_limit`` to be passed to the underlying
|
||||
@@ -2034,7 +2011,6 @@
|
||||
.. change::
|
||||
:tags: bug, mysql
|
||||
:tickets: 2771
|
||||
:pullreq: bitbucket:49
|
||||
|
||||
Fixes to fully support using the ``'utf8mb4'`` MySQL-specific charset
|
||||
with MySQL dialects, in particular MySQL-Python and PyMySQL. In
|
||||
@@ -2077,7 +2053,6 @@
|
||||
.. change::
|
||||
:tags: bug, orm
|
||||
:tickets: 3327
|
||||
:pullreq: github:160
|
||||
|
||||
Fixed unexpected use regression from pullreq github:137 where
|
||||
Py2K unicode literals (e.g. ``u""``) would not be accepted by the
|
||||
@@ -2197,7 +2172,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:pullreq: github:132
|
||||
|
||||
The PG8000 dialect now supports the
|
||||
:paramref:`.create_engine.encoding` parameter, by setting up
|
||||
@@ -2206,7 +2180,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:pullreq: github:132
|
||||
|
||||
Added support for PG8000's native JSONB feature. Pull request
|
||||
courtesy Tony Locke.
|
||||
@@ -2266,7 +2239,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, oracle
|
||||
:pullreq: github:152
|
||||
|
||||
Added support for cx_oracle connections to a specific service
|
||||
name, as opposed to a tns name, by passing ``?service_name=<name>``
|
||||
@@ -2312,7 +2284,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql, pypy
|
||||
:tickets: 3052
|
||||
:pullreq: bitbucket:34
|
||||
|
||||
Added support for the psycopg2cffi DBAPI on pypy. Pull request
|
||||
courtesy shauns.
|
||||
@@ -2324,7 +2295,6 @@
|
||||
.. change::
|
||||
:tags: feature, orm
|
||||
:tickets: 3262
|
||||
:pullreq: bitbucket:38
|
||||
|
||||
A warning is emitted when the same polymorphic identity is assigned
|
||||
to two different mappers in the same hierarchy. This is typically a
|
||||
@@ -2334,7 +2304,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, sql
|
||||
:pullreq: github:150
|
||||
|
||||
The type of expression is reported when an object passed to a
|
||||
SQL expression unit can't be interpreted as a SQL fragment;
|
||||
@@ -2682,7 +2651,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, sql
|
||||
:pullreq: github:146
|
||||
|
||||
Fixed the name of the :paramref:`.PoolEvents.reset.dbapi_connection`
|
||||
parameter as passed to this event; in particular this affects
|
||||
@@ -2691,7 +2659,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, sql
|
||||
:pullreq: github:139
|
||||
|
||||
Added a new parameter :paramref:`.Table.tometadata.name` to
|
||||
the :meth:`.Table.tometadata` method. Similar to
|
||||
@@ -2703,7 +2670,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: bug, orm
|
||||
:pullreq: github:137
|
||||
|
||||
Repaired support of the ``copy.deepcopy()`` call when used by the
|
||||
:class:`.orm.util.CascadeOptions` argument, which occurs
|
||||
@@ -2861,7 +2827,6 @@
|
||||
.. change::
|
||||
:tags: feature, sql
|
||||
:tickets: 3184
|
||||
:pullreq: bitbucket:30
|
||||
|
||||
The :class:`.UniqueConstraint` construct is now included when
|
||||
reflecting a :class:`.Table` object, for databases where this
|
||||
@@ -2892,7 +2857,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:pullreq: github:134
|
||||
|
||||
Added support for the FILTER keyword as applied to aggregate
|
||||
functions, supported by Postgresql 9.4. Pull request
|
||||
@@ -2978,7 +2942,6 @@
|
||||
.. change::
|
||||
:tags: bug, sqlite
|
||||
:tickets: 3203
|
||||
:pullreq: bitbucket:31
|
||||
|
||||
SQLite now supports reflection of unique constraints from
|
||||
temp tables; previously, this would fail with a TypeError.
|
||||
@@ -3010,7 +2973,6 @@
|
||||
.. change::
|
||||
:tags: feature, postgresql
|
||||
:tickets: 2891
|
||||
:pullreq: github:128
|
||||
|
||||
Support has been added for reflection of materialized views
|
||||
and foreign tables, as well as support for materialized views
|
||||
@@ -3350,7 +3312,6 @@
|
||||
.. change::
|
||||
:tags: sql, feature
|
||||
:tickets: 3027
|
||||
:pullrequest: bitbucket:29
|
||||
|
||||
The :paramref:`.Table.autoload_with` flag now implies that
|
||||
:paramref:`.Table.autoload` should be ``True``. Pull request
|
||||
@@ -3358,7 +3319,6 @@
|
||||
|
||||
.. change::
|
||||
:tags: postgresql, feature
|
||||
:pullreq: github:126
|
||||
|
||||
Added new method :meth:`.PGInspector.get_enums`, when using the
|
||||
inspector for Postgresql will provide a list of ENUM types.
|
||||
|
||||
Vendored
+2
-3
@@ -65,9 +65,8 @@ changelog_inner_tag_sort = ["feature", "changed", "removed", "bug", "moved"]
|
||||
changelog_render_ticket = "http://www.sqlalchemy.org/trac/ticket/%s"
|
||||
|
||||
changelog_render_pullreq = {
|
||||
"bitbucket": "https://bitbucket.org/zzzeek/sqlalchemy/pull-request/%s",
|
||||
"default": "https://bitbucket.org/zzzeek/sqlalchemy/pull-request/%s",
|
||||
"github": "https://github.com/zzzeek/sqlalchemy/pull/%s",
|
||||
"default": "https://github.com/sqlalchemy/sqlalchemy/pull/%s",
|
||||
"github": "https://github.com/sqlalchemy/sqlalchemy/pull/%s",
|
||||
}
|
||||
|
||||
changelog_render_changeset = "http://www.sqlalchemy.org/trac/changeset/%s"
|
||||
|
||||
Vendored
+2
-2
@@ -425,7 +425,7 @@ parameters which create :class:`.UniqueConstraint` and :class:`.Index` objects
|
||||
without an explicit name being specified.
|
||||
|
||||
The use case of alteration of existing tables and constraints can be handled
|
||||
by schema migration tools such as `Alembic <http://alembic.zzzcomputing.com/>`_.
|
||||
by schema migration tools such as `Alembic <https://alembic.sqlalchemy.org/>`_.
|
||||
However, neither Alembic nor SQLAlchemy currently create names for constraint
|
||||
objects where the name is otherwise unspecified, leading to the case where
|
||||
being able to alter existing constraints means that one must reverse-engineer
|
||||
@@ -560,7 +560,7 @@ name as follows::
|
||||
:paramref:`.MetaData.naming_convention` - for additional usage details
|
||||
as well as a listing of all available naming components.
|
||||
|
||||
:ref:`alembic:tutorial_constraint_names` - in the Alembic documentation.
|
||||
`The Importance of Naming Constraints <https://alembic.sqlalchemy.org/en/latest/naming.html>`_ - in the Alembic documentation.
|
||||
|
||||
.. versionadded:: 0.9.2 Added the :paramref:`.MetaData.naming_convention` argument.
|
||||
|
||||
|
||||
Vendored
+3
-5
@@ -243,16 +243,14 @@ database schemas in relation to application code using schema migration tools.
|
||||
|
||||
There are two major migration tools available for SQLAlchemy:
|
||||
|
||||
* `Alembic <http://alembic.zzzcomputing.com>`_ - Written by the author of SQLAlchemy,
|
||||
* `Alembic <https://alembic.sqlalchemy.org>`_ - Written by the author of SQLAlchemy,
|
||||
Alembic features a highly customizable environment and a minimalistic usage pattern,
|
||||
supporting such features as transactional DDL, automatic generation of "candidate"
|
||||
migrations, an "offline" mode which generates SQL scripts, and support for branch
|
||||
resolution.
|
||||
* `SQLAlchemy-Migrate <https://github.com/openstack/sqlalchemy-migrate>`_ - The original
|
||||
migration tool for SQLAlchemy, SQLAlchemy-Migrate is widely used and continues
|
||||
under active development. SQLAlchemy-Migrate includes features such as
|
||||
SQL script generation, ORM class generation, ORM model comparison, and extensive
|
||||
support for SQLite migrations.
|
||||
migration tool for SQLAlchemy, SQLAlchemy-Migrate is still used by projects
|
||||
such as Openstack, however is being superseded by Alembic.
|
||||
|
||||
|
||||
Specifying the Schema Name
|
||||
|
||||
Vendored
+1
-1
@@ -88,7 +88,7 @@ metadata creation sequence, using this recipe::
|
||||
engine = create_engine('postgresql://', strategy='mock', executor=dump)
|
||||
metadata.create_all(engine, checkfirst=False)
|
||||
|
||||
The `Alembic <https://bitbucket.org/zzzeek/alembic>`_ tool also supports
|
||||
The `Alembic <https://alembic.sqlalchemy.org>`_ tool also supports
|
||||
an "offline" SQL generation mode that renders database migrations as SQL scripts.
|
||||
|
||||
How can I subclass Table/Column to provide certain behaviors/configurations?
|
||||
|
||||
Reference in New Issue
Block a user