summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 0.7.6rel_0_7_6Mike Bayer2015-05-051-0/+1
|
* Merged in jdanjou/alembic/jd/typo-doc-comparator (pull request #44)Mike Bayer2015-05-041-1/+1
|\ | | | | | | Fix typo in autogenerate documentation
| * Fix typo in autogenerate documentationJulien Danjou2015-05-041-1/+1
|/
* - Fixed bug where the case of multiple mergepoints that allMike Bayer2015-05-033-7/+170
| | | | | | | | | | | have the identical set of ancestor revisions would fail to be upgradable, producing an assertion failure. Merge points were previously assumed to always require at least an UPDATE in alembic_revision from one of the previous revs to the new one, however in this case, if one of the mergepoints has already been reached, the remaining mergepoints have no row to UPDATE therefore they must do an INSERT of their target version. fixes #297
* - add tox targets for 3.4Mike Bayer2015-05-011-1/+7
|
* - Added support for type comparison functions to be not just perMike Bayer2015-04-305-33/+124
| | | | | | | | environment, but also present on the custom types themselves, by supplying a method ``compare_against_backend``. Added a new documentation section :ref:`compare_types` describing type comparison fully. fixes #296
* Merged in rtaranu/alembic (pull request #43)Mike Bayer2015-04-211-1/+1
|\ | | | | | | - fixed spelling mistake in docs
| * - fixed spelling mistake in docsRaul Taranu2015-04-211-1/+1
|/
* - Added a new optionMike Bayer2015-04-0712-54/+170
| | | | | | | | | | | | | | | | | | | :paramref:`.EnvironmentContext.configure.literal_binds`, which will pass the ``literal_binds`` flag into the compilation of SQL constructs when using "offline" mode. This has the effect that SQL objects like inserts, updates, deletes as well as textual statements sent using ``text()`` will be compiled such that the dialect will attempt to render literal values "inline" automatically. Only a subset of types is typically supported; the :meth:`.Operations.inline_literal` construct remains as the construct used to force a specific literal representation of a value. The :paramref:`.EnvironmentContext.configure.literal_binds` flag is added to the "offline" section of the ``env.py`` files generated in new environments. fixes #255 - enhance the op_fixture as well as MigrationContext._stdout_connection() so that it uses the real DefaultImpl and MigrationContext fully in tests.
* - repair name of starting_rev argument, fixes #290Mike Bayer2015-03-291-1/+1
|
* - dont rely on inpsect import, not in SQLA 0.7Mike Bayer2015-03-281-4/+3
|
* - don't use op.f(), only works with later SQLA versionsMike Bayer2015-03-281-4/+4
|
* - Fully implemented theMike Bayer2015-03-277-11/+182
| | | | | | | | | | :paramref:`~.Operations.batch_alter_table.copy_from` parameter for batch mode, which previously was not functioning. This allows "batch mode" to be usable in conjunction with ``--sql``. fixes #289 - sqlite dialect checks for "create_index" and "drop_index" as exceptions for "recreate" in batch mode, the same way as "add_column", so that unnecessary table recreates don't emit for index-only operations
* - next versionMike Bayer2015-03-271-1/+1
|
* - Repaired support for the :meth:`.BatchOperations.create_index`Mike Bayer2015-03-273-3/+57
| | | | | | directive, which was mis-named internally such that the operation within a batch context could not proceed. fixes #287
* - didn't name the internal number correctly, stilrel_0_7_5_post2Mike Bayer2015-03-201-1/+1
| | | | don't have this right. up to post2
* - 0.7.5.post1 due to pypi deletion issuerel_0_7_5_post1Mike Bayer2015-03-201-1/+1
|
* 0.7.5rel_0_7_5Mike Bayer2015-03-191-0/+1
|
* - changelog for #266Mike Bayer2015-03-193-8/+21
| | | | | | | - use exception fixture - look directly at context.as_sql as that's where the "sql mode" is most authoritative - fixes #266
* Merge branch 'issue266' of https://bitbucket.org/jerdfelt/alembic into pr39Mike Bayer2015-03-192-0/+22
|\
| * Raise exception if autogenerate is tried with as_sql=TrueJohannes Erdfelt2015-02-232-0/+22
| | | | | | | | | | | | | | This configuration is nonsensical since autogenerate needs to query the database for schema information. Fixes issue #266
* | - Fixed bug where the mssql DROP COLUMN directive failed to includeMike Bayer2015-03-113-1/+13
| | | | | | | | | | modifiers such as "schema" when emitting the DDL. fixes #284
* | - an adjustment to the logic for #282 - if the index we see hereMike Bayer2015-03-101-0/+2
| | | | | | | | *is* in conn_indexes_by_name, then obviously we should leave it in.
* | - Postgresql "functional" indexes are necessarily skipped from theMike Bayer2015-03-103-2/+58
| | | | | | | | | | | | | | | | autogenerate process, as the SQLAlchemy backend currently does not support reflection of these structures. A warning is emitted both from the SQLAlchemy backend as well as from the Alembic backend for Postgresql when such an index is detected. fixes #282
* | - add support for assertion of warnings emittedMike Bayer2015-03-101-0/+117
| |
* | - make the repo dynamicMike Bayer2015-03-101-4/+6
|/
* - Fixed bug where MySQL backend would report dropped unique indexesMike Bayer2015-02-204-7/+75
| | | | | | | | | | | | | and/or constraints as both at the same time. This is because MySQL doesn't actually have a "unique constraint" construct that reports differently than a "unique index", so it is present in both lists. The net effect though is that the MySQL backend will report a dropped unique index/constraint as an index in cases where the object was first created as a unique constraint, if no other information is available to make the decision. This differs from other backends like Postgresql which can report on unique constraints and unique indexes separately. fixes #276
* - additional fix which impacts #267. fix filtered_heads() to accommodateMike Bayer2015-02-083-3/+15
| | | | | being given "heads" as the target so that it will in fact match when all heads are given. fixes #267
* - move resolution of "starting rev" for --sql mode intoMike Bayer2015-02-034-7/+58
| | | | | | | | | | | | | | get_current_heads() directly; therefore we don't need to do this in alembic.command, which we were doing for stamp but not downgrade/upgrade. The slight change here is that the context.get_starting_revision_argument() method will return an abbreviated starting rev as abbreviated in all cases, including the stamp command, where we previously were converting a stamp argument first, but not for the upgrade or downgrade commands. - Fixed bug where using a partial revision identifier as the "starting revision" in ``--sql`` mode in a downgrade operation would fail to resolve properly. fixes #269
* remove errant pdbMike Bayer2015-01-231-3/+0
|
* - Added a new feature :attr:`.Config.attributes`, to help with the useMike Bayer2015-01-239-39/+187
| | | | | | case of sharing state such as engines and connections on the outside with a series of Alembic API calls; also added a new cookbook section to describe this simple but pretty important use case.
* fix missing changelog directiveMike Bayer2015-01-231-0/+1
|
* - Added support for "alembic stamp" to work when given "heads" as anMike Bayer2015-01-233-38/+72
| | | | | argument, when multiple heads are present. fixes #267
* - set up for next revMike Bayer2015-01-231-3/+3
|
* - fix all flake8Mike Bayer2015-01-231-187/+116
|
* - the enum render is an 0.9 regression, apparently we usedMike Bayer2015-01-133-2/+14
| | | | a different repr() scheme in 0.7.9->0.8 that didn't omit native_enum
* - 0.7.4rel_0_7_4Mike Bayer2015-01-121-1/+2
|
* - happy new yearMike Bayer2015-01-122-2/+2
|
* changelog for #241, fixes #241Mike Bayer2015-01-121-0/+11
|
* Merge https://bitbucket.org/dtheodor/alembic/branch/master into pr37Mike Bayer2015-01-122-5/+72
|\
| * remove redundant Float type checkDimitris Theodorou2015-01-121-2/+2
| |
| * Change single-quoting of floats in PostgreSQL compare_server_defaultDimitris Theodorou2015-01-122-5/+72
| | | | | | | | | | | | | | | | | | Do not wrap string defaults with single quotes when comparing against columns of type float or numeric. This fixes the crash occuring when the default of a float column is an integer value (e.g., DEFAULT 5), while the Python server_default is a string (e.g., server_default="5.0"). This results in the query used in the comparison to throw a DataError ('SELECT 5 = '5.0').
* | checked test failureDimitris Theodorou2015-01-123-0/+11
| |
* | Enum autogenerate renders the native_enum flag as wellDimitris Theodorou2015-01-121-0/+6
|/
* - The rendering of a :class:`~sqlalchemy.schema.ForeignKeyConstraint`Mike Bayer2015-01-103-7/+91
| | | | | | | | | | | will now ensure that the names of the source and target columns are the database-side name of each column, and not the value of the ``.key`` attribute as may be set only on the Python side. This is because Alembic generates the DDL for constraints as standalone objects without the need to actually refer to an in-Python :class:`~sqlalchemy.schema.Table` object, so there's no step that would resolve these Python-only key names to database column names. fixes #259
* - Fixed bug in foreign key autogenerate where if the in-Python tableMike Bayer2015-01-104-2/+122
| | | | | | | | | | | used custom column keys (e.g. using the ``key='foo'`` kwarg to ``Column``), the comparison of existing foreign keys to those specified in the metadata would fail, as the reflected table would not have these keys available which to match up. Foreign key comparison for autogenerate now ensures it's looking at the database-side names of the columns in all cases; this matches the same functionality within unique constraints and indexes. fixes #260
* - make this test use legal table designsMike Bayer2015-01-101-6/+4
|
* - add/remove seemed backwards hereMike Bayer2015-01-101-4/+4
|
* - changelog: Fixed issue in autogenerate type rendering where types that belongMike Bayer2015-01-093-3/+37
| | | | | | to modules that have the name "sqlalchemy" in them would be mistaken as being part of the ``sqlalchemy.`` namespace. Pull req courtesy Bartosz Burclaf. fixes #261
* Fixes user module namespace for custom typesBartosz Burclaf2015-01-091-1/+1
|
View Lorry Controller Status