summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* 0.7.3rel_0_7_3Mike Bayer2014-12-301-0/+1
|
* - Fixed regression in new versioning system where upgrade / historyMike Bayer2014-12-304-4/+45
| | | | | | operation would fail on AttributeError if no version files were present at all. fixes #258
* - put sqlalchemy master here as SQLA issue ↵Mike Bayer2014-12-192-1/+1
| | | | | | https://bitbucket.org/zzzeek/sqlalchemy/issue/3218 is blowing up our sphinx build
* 0.7.2rel_0_7_2Mike Bayer2014-12-181-0/+1
|
* - Adjusted the SQLite backend regarding autogen of unique constraintsMike Bayer2014-12-143-11/+20
| | | | | | | to work fully with the current SQLAlchemy 1.0, which now will report on UNIQUE constraints that have no name. - fix named foreign key test requirements for SQLAlchemy 1.0 sqlite FK reflection
* - identify a test that can't pass on 0.8 for nowMike Bayer2014-12-131-0/+3
|
* - also add an explicit schema test for the multi fk conditionMike Bayer2014-12-131-24/+49
|
* - Fixed bug in batch where if the target table contained multipleMike Bayer2014-12-133-6/+51
| | | | | | foreign keys to the same target table, the batch mechanics would fail with a "table already exists" error. Thanks for the help on this from Lucas Kahlert. fixes #254
* -Repaired a regression in both the MSSQL and Oracle dialects wherebyMike Bayer2014-12-125-4/+14
| | | | | | | the overridden ``_exec()`` method failed to return a value, as is needed now in the 0.7 series. fixes #253 - add __backend__ to UpdateRevTest which does a great job testing _exec() pathing for all backends
* - adjust test here so that it applies to all backendsMike Bayer2014-12-044-21/+35
| | | | | | - skip index at the level of the index, not the columns inside it - changelog - bump for 0.7.2
* Merge branch 'mysql-unique-index-removed' of ↵Mike Bayer2014-12-042-0/+21
|\ | | | | | | https://bitbucket.org/jerdfelt/alembic into pr35
| * MySQL: Ignore unique indexes when removing implicit indexesJohannes Erdfelt2014-12-042-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MySQL will implicitly create indexes when using foreign keys. Alembic attempts to remove those implicit indexes so they don't appear as removes when comparing metadata. However, unique indexes with the same name as a column are considered as possibly implicitly created causing alembic to emit a spurious 'remove_constraint'. Since MySQL will never implicitly create unique indexes, they can be safely ignored when removing the implicit indexes. Fixes #251
* | 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
View Lorry Controller Status