summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* python-editor 0.3 fixed a bug with using nano.edit-latestMichel Albert2015-07-171-1/+1
|
* Reusing existing compat. code from alembic.testing.Michel Albert2015-07-161-8/+3
|
* Replaced hand-crafted code with python-editor.Michel Albert2015-07-167-120/+17
|
* Removed arguments for "--edit" command.Michel Albert2015-07-161-7/+0
|
* New CLI command: "edit" - Edits the latest rev.Michel Albert2015-07-156-0/+163
| | | | Running ``alembic edit`` will open the latest revision in a text-editor.
* - some additional namesMike Bayer2015-07-143-3/+30
| | | | - warn for name changes
* - handle missing arg more clearlyMike Bayer2015-07-143-2/+40
| | | | - add missing translate for create_pk
* - move the "legacy names" system into where we create the module proxy.Mike Bayer2015-07-144-48/+62
| | | | | | | | | This is so that we can do a total open ended "*args, **kw" style translation for the vast majority of use cases that are using alembic.op, without impacting docstrings for the Operations class. There is a risk here of impacting an application that is using Operations directly instantitaed while using old names. We may still have to accommodate that somehow.
* - Implemented support for :meth:`.BatchOperations.create_primary_key`Mike Bayer2015-07-038-10/+150
| | | | | | | and :meth:`.BatchOperations.create_check_constraint`. fixes #305 - table keyword arguments are copied from the original reflected table, such as the "mysql_engine" keyword argument.
* Index didn't have a quote parameter until 0.9, when the quote param isMike Bayer2015-07-031-7/+5
| | | | | portable to the name itself. so we don't need to handle this arg explicitly.
* - try to explain this betterMike Bayer2015-07-032-13/+29
|
* - add the .info dictionary, references #302Mike Bayer2015-07-031-0/+8
|
* - squash merge of ticket_302 branchMike Bayer2015-07-0373-3300/+6865
| | | | | | | | | | | - The internal system for Alembic operations has been reworked to now build upon an extensible system of operation objects. New operations can be added to the ``op.`` namespace, including that they are available in custom autogenerate schemes. fixes #302 - The internal system for autogenerate been reworked to build upon the extensible system of operation objects present in #302. A new customization hook process_revision_directives is added to allow manipulation of the autogen stream. Fixes #301
* - add a changelog for the legacy_schema_aliasing warning issue,Mike Bayer2015-06-261-0/+7
| | | | the fix was committed in 229f8672.
* - add clarification that this tutorial is against the generic templateMike Bayer2015-06-171-1/+10
|
* - The :meth:`.MigrationContext.stamp` method, added as part of theMike Bayer2015-06-093-1/+30
| | | | | | | | versioning refactor in 0.7 as a more granular version of :func:`.command.stamp`, now includes the "create the alembic_version table if not present" step in the same way as the command version, which was previously omitted. fixes #300
* - turn on the mssql legacy_schema_aliasing flag to removeMike Bayer2015-05-263-1/+8
| | | | warnings
* - Fixed bug where foreign key options including "onupdate",Mike Bayer2015-05-184-13/+106
| | | | | | | "ondelete" would not render within the ``op.create_foreign_key()`` directive, even though they render within a full ``ForeignKeyConstraint`` directive. fixes #298
* - add test for FKC with multiple kwargs, reference #92Mike Bayer2015-05-181-0/+15
|
* 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.
View Lorry Controller Status