delta/python-packages/sqlalchemy-migrate.git/migrate, branch master

Retire github mirror, repo moved to opendev

2019-09-26T13:56:42+00:00

Merge "Import MutableMapping from the correct Python module"

2019-01-21T22:17:29+00:00

Merge "Don't use deprecated / non-functional "force" parameter"

2019-01-21T22:13:03+00:00

Don't use deprecated / non-functional "force" parameter

2019-01-18T18:11:40+00:00

The "force" parameter in SQLAlchemy IdentifierPreparer.quote()
has been a no-op since 0.9 in
https://github.com/sqlalchemy/sqlalchemy/commit/031ef0807838842a827135dbace760da7aec215e,
which was six years ago.   In SQLAlchemy 1.3 this parameter
will be removed entirely.   Bump requirements to 0.9 series
here and remove usage of the "force" flag.

Change-Id: I4492df2e7d2075fefbf13d6782de11f7d402f6b8

Use legacy_alter_table ON in sqlite recreate_table

2019-01-15T22:01:26+00:00

Use "PRAGMA legacy_alter_table = ON" with sqlite >= 3.26 when
using "ALTER TABLE RENAME TO migration_tmp" to maintain legacy
behavior.

As of sqlite version 3.26, when a table is renamed using
"ALTER TABLE RENAME TO", REFERENCES clauses that refer to the
table will be updated. To maintain legacy (3.24 and earlier)
behavior, "PRAGMA legacy_alter_table" can be set to true and
"PRAGMA foreign_keys" can be set to false. [1]

[1] https://www.sqlite.org/src/info/ae9638e9c0ad0c36

Thanks to "László Böszörményi (GCS)"  for
providing the code for this patch, which has since been
slightly modified.

Change-Id: I539988ab2ad6df6c8f423ecec15364ad8fcc7267
Closes-Bug: 1807262

Import MutableMapping from the correct Python module

2019-01-15T18:16:06+00:00

Change-Id: Ifb66fe22bc607b13f5c4756d3b93f5e8206c33e3

Merge "Fix spelling mistake"

2017-03-24T21:23:38+00:00

Fix spelling mistake

2016-10-26T14:27:24+00:00

TrivialFix

Change-Id: I089d9e8b57895d9878bf82d2fac397722fccc083

Set autoincrement to False when modifying to non-Integer datatype

2016-10-20T21:47:19+00:00

Starting in SQLAlchemy 1.1, the rules for when "autoincrement=True"
may be set on a column are more strict.  The migrate tests are
testing the alteration of a column from Integer to String
and then regenerating; this means we need to set autoincrement
to False as well.   A related issue in SQLAlchemy 1.1 is
also being fixed (see https://bitbucket.org/zzzeek/sqlalchemy/issues/3835/),
however this fix is not needed in order for the tests to pass here.

Change-Id: Ibd3a75fff13312411df87e17b6e5764865d69728

Merge "Raise VersionNotFoundError instead of KeyError"

2016-06-03T13:45:36+00:00