summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* 0.7.1rel_0_7_1Mike Bayer2014-12-031-0/+1
|
* - The ``render_as_batch`` flag was inadvertently hardcoded to ``True``,Mike Bayer2014-12-032-1/+8
| | | | | so all autogenerates were spitting out batch mode...this has been fixed so that batch mode again is only when selected in env.py.
* - use a much bigger stamp here as only three chars can collide quite easilyMike Bayer2014-12-011-1/+1
|
* 0.7.1Mike Bayer2014-11-301-1/+1
|
* - repair the rendering of add_fk_constraint(), quoting there tooMike Bayer2014-11-303-8/+37
|
* - naming convention limited to SQLA 0.9.4 or greaterMike Bayer2014-11-303-1/+5
|
* - fix drop_foreign_key to include that this only works with SQLiteMike Bayer2014-11-302-1/+10
| | | | as stated
* - reword the first paragraph about offline mode to better flowMike Bayer2014-11-301-5/+7
| | | | from the preceding sections.
* - Added :paramref:`~.Operations.batch_alter_table.naming_convention`Mike Bayer2014-11-305-32/+152
| | | | | | | | | argument to :meth:`.Operations.batch_alter_table`, as this is necessary in order to drop foreign key constraints; these are often unnamed on the target database, and in the case that they are named, SQLAlchemy is as of the 0.9 series not including these names yet. - rework the docs on batch + constraints, which remains subject to a lot of caveats and problems, some to be resolved in SQLAlchemy 1.0
* - name the include_object hook "foreign_key_constraint"Mike Bayer2014-11-306-12/+66
| | | | | - changelog and other doc updates, fixes #178 - fix drop_constraint() unit tests and add two more for FKs
* - refactor the FK merge a bitMike Bayer2014-11-308-166/+469
| | | | | | | | | | | | | | | | | | | | - getting at attributes of FKs varies a bit on SQLA versions, so implement an _fk_spec() called for all FK inspection - to enable include_object() filters and allow the FK constraint code to flow like that of indexes/uniques, change the approach so that we deal with an _fk_constraint_sig() object again which contains the real ForeignKeyConstraint() within; we need this anyway for include_object, but also allows us to use the standard "drop_constraint" call for rendering. - enhance tests in test_autogen_fks to support real FK databases like Postgresql, MySQL, add in InnoDB flags and ensure that FKs refer to real primary key constraints for PG support - implement and test include_object() support for FKs - inspectors all have get_foreign_keys(), no need to check - repair the drop_constraint call to quote the "type" and table name correctly, run all constraint drops through drop_constraint() for rendering - fix up schema identifiers for foreign key autogens
* - Merge branch 'add_fk_check' of https://bitbucket.org/akamyshnikova/alembic ↵Mike Bayer2014-11-305-41/+385
|\ | | | | | | | | | | | | | | | | | | | | into pr32 - complete merge, get all tests passing - use 'foreignkey' literal Conflicts: alembic/autogenerate/compare.py tests/test_autogenerate.py
| * Fix failing unittests and update compare_fk methodAnn Kamyshnikova2014-11-252-24/+36
| |
| * Some refactor of _add_fk_constraintAnn Kamyshnikova2014-11-131-5/+12
| |
| * Add _add_fk_constraint and _drop_fk_constraint to renderAnn Kamyshnikova2014-11-113-5/+23
| |
| * Add composite fk support, add more testsAnn Kamyshnikova2014-11-072-6/+159
| |
| * Update and add some tests for checking fkAnn Kamyshnikova2014-11-075-28/+123
| | | | | | | | fixes issue #178
| * Implement autogenerate detection for foreign key constraintsAnn Kamyshnikova2014-11-051-0/+45
| | | | | | | | Issue #178
* | - Fixed bug where the "source_schema" argument was not correctly passedMike Bayer2014-11-302-4/+65
| | | | | | | | | | | | when calling :meth:`.BatchOperations.create_foreign_key`. Pull request courtesy Malte Marquarding. - add tests
* | Merge branch 'master' of https://bitbucket.org/mmarquar/alembicMike Bayer2014-11-301-1/+1
|\ \
| * | Fix source_schema argument in BatchOperation.create_foreign_keyMalte Marquarding2014-11-281-1/+1
| | |
* | | - Repaired the inspection, copying and rendering of CHECK constraintsMike Bayer2014-11-298-20/+360
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | and so-called "schema" types such as Boolean, Enum within the batch copy system; the CHECK constraint will not be "doubled" when the table is copied, and additionally the inspection of the CHECK constraint for its member columns will no longer fail with an attribute error. fixes #249 - Added two new arguments :paramref:`.Operations.batch_alter_table.reflect_args` and :paramref:`.Operations.batch_alter_table.reflect_kwargs`, so that arguments may be passed directly to suit the :class:`~.sqlalchemy.schema.Table` object that will be reflected.
* | fix symbolMike Bayer2014-11-261-1/+1
| |
* | 0.7.0rel_0_7_0Mike Bayer2014-11-241-0/+1
| |
* | fix manifestMike Bayer2014-11-241-1/+1
| |
* | - test runner updatesMike Bayer2014-11-241-4/+5
| |
* | - add a missing @classmethod decorator...Mike Bayer2014-11-241-0/+1
| |
* | - The ``alembic revision`` command accepts the ``--sql`` option toMike Bayer2014-11-233-0/+43
| | | | | | | | | | | | | | | | | | | | | | suit some very obscure use case where the ``revision_environment`` flag is set up, so that ``env.py`` is run when ``alembic revision`` is run even though autogenerate isn't specified. As this flag is otherwise confusing, error messages are now raised if ``alembic revision`` is invoked with both ``--sql`` and ``--autogenerate`` or with ``--sql`` without ``revision_environment`` being set. fixes #248
* | - Relative revision identifiers as used with ``alembic upgrade``,Mike Bayer2014-11-236-58/+174
| | | | | | | | | | | | ``alembic downgrade`` and ``alembic history`` can be combined with specific revisions as well, e.g. ``alembic upgrade ae10+3``, to produce a migration target relative to the given exact version.
* | - ensure we include for dependencies when we do a stamp, add an optionMike Bayer2014-11-233-6/+16
| | | | | | | | to filter_for_lineage
* | - use the correct method here; this needs to have some testsMike Bayer2014-11-231-1/+1
| |
* | yikes forgot batch modeMike Bayer2014-11-221-0/+1
| |
* | - spiff up autogenerate docs a bitMike Bayer2014-11-221-83/+138
| |
* | - add another test around something that is bugging/confusing me...Mike Bayer2014-11-221-0/+66
| | | | | | | | but i guess it's OK
* | - fixesMike Bayer2014-11-226-35/+74
| |
* | tuple form as wellMike Bayer2014-11-221-1/+9
| |
* | - now that branching is an enormous chapter, break out the docs intoMike Bayer2014-11-228-1670/+1685
| | | | | | | | | | individual pages. the pages here are a little slim in the middle but overall the one-page docs were getting extremely long.
* | - add the refMike Bayer2014-11-221-0/+2
| |
* | - In conjunction with support for multiple independent bases, theMike Bayer2014-11-2211-168/+488
| | | | | | | | | | | | | | | | | | | | specific version directories are now also configurable to include multiple, user-defined directories. When multiple directories exist, the creation of a revision file with no down revision requires that the starting directory is indicated; the creation of subsequent revisions along that lineage will then automatically use that directory for new files. fixes #124
* | - break out the concept of "down revision" into two pieces:Mike Bayer2014-11-224-49/+305
| | | | | | | | | | | | | | | | down_revision and "dependencies". For migration traversal, the downrevs we care about are the union of these two sets. however for location of nodes and branch labeling, we look only at down_revsion. this works really well and allows us to have mutually-dependent trees that can easily be itererated independently of each other. docs are needed
* | - support the case where a mergepoint has a branchpoint immediatelyMike Bayer2014-11-222-40/+238
| | | | | | | | | | | | | | | | following it; this will be the norm in the case where parallel branches refer to each other as dependencies. this means we need to limit for from/to revisions based on current heads / ancestors of those heads whenever we merge/unmerge.
* | - modernize the readme especially the SQLite thingMike Bayer2014-11-211-19/+20
| |
* | ModelOne now has unique constraints so require thatMike Bayer2014-11-211-0/+2
| |
* | - add more label syntaxesMike Bayer2014-11-211-0/+20
| |
* | - Added a rule for Postgresql to not render a "drop unique" and "drop index"Mike Bayer2014-11-215-0/+54
| | | | | | | | | | | | | | | | given the same name; for now it is assumed that the "index" is the implicit one Postgreql generates. Future integration with new SQLAlchemy 1.0 features will improve this to be more resilient. fixes #247
* | include indexes in batchMike Bayer2014-11-215-49/+129
| |
* | - A change in the ordering when columns and constraints are dropped;Mike Bayer2014-11-213-69/+120
| | | | | | | | | | | | | | autogenerate will now place the "drop constraint" calls *before* the "drop column" calls, so that columns involved in those constraints still exist when the constraint is dropped. fixes #247
* | make the three way merge thing a separate section, we don't reallyMike Bayer2014-11-201-13/+16
| | | | | | | | even need it but should be fine
* | - typoMike Bayer2014-11-201-2/+2
| |
* | put the sqlite thing near the top as it's the other big featureMike Bayer2014-11-201-30/+30
| |