summaryrefslogtreecommitdiff
path: root/migrate
Commit message (Collapse)AuthorAgeFilesLines
...
| * | UniqueConstraint named and escaped twiceThomas Goirand2014-03-021-1/+1
| |/ | | | | | | | | | | | | | | This patch fixes get_constraint_name in the ANSIConstraintCommon class. It's part of the fixes needed for SQLA 0.9.x compat. Change-Id: I1f1648af48f459bd18f99bb42fa9a272186fb37d
* | Conditionally import ibmdb2/ibm_db_saMatt Riedemann2014-03-041-3/+11
|/ | | | | | | | | | Since ibm_db_sa is not part of sqlalchemy, we need to handle the conditional import of the module in visitor.py so we don't get an ImportError if ibm_db_sa is not available. Closes-Bug: #1287229 Change-Id: Ida070b629ce3b9be727ae49973bb6a71543c1dcf
* Add DB2 10.5 SupportMatt Riedemann2014-02-1710-15/+393
| | | | | | | | | | | | | | | | | | This patch adds the initial support for DB2 10.5 to migrate. It includes: 1. The dialect implementation for DB2. 2. The dialect registration with the visitor. 3. Code to parse the engine name in version.py. 4. A new dependency on ibm_db_sa in test-requirements.txt. 5. A connection string in test_db.cfg for ibm_db_sa. Part of blueprint add-db2-support Co-authored-by: Sheng Bo Hou <sbhou@cn.ibm.com> Co-authored-by: Thuy Christenson <thuy@us.ibm.com> Co-authored-by: Rahul Priyadarshi <rahul.priyadarshi@in.ibm.com> Change-Id: I745ec615487b1b06c5d1a09ea316f376d66ee4c0
* Un-break the version in migrate/__init__.py0.8.2Monty Taylor2013-11-151-1/+4
| | | | Change-Id: Ie642315c20866435a709d576c99d6e293e7a7e63
* Fix the version number to match the last release.Dan Prince2013-11-151-1/+1
| | | | | | | ** NOTE: our release process really should do this ahead of time. Change-Id: Ic0cce0d57b4f05092417c4cf1a4ca5a74812ec3c
* Fix int overflow exception in unittest0.8Matt Riedemann2013-11-061-2/+17
| | | | | | | | | | | | | | | | | | Fixes: File ".../versioning/version.py", line 30, in __init__ if self < 0: OverflowError: Python int too large to convert to C long Don't use __cmp__ which is deprecated and restricted to C long ints, rather than python's arbitrary precision ints. Copied from Pádraig Brady's Fedora patch: http://pkgs.fedoraproject.org/cgit/python-migrate.git/commit/?id=a01bf449 Co-authored-by: Pádraig Brady <pbrady@redhat.com> Change-Id: I71f349f97507525b2f2edaf034005d67b6cc3987
* Fix dropping of indexed columns in sqlite/sa08Roman Podolyaka2013-10-183-3/+39
| | | | | | | | | | | | | | | | | | | | | | | | | Version 0.8 of SQLAlchemy added support of indexes on expressions in addition to plain table columns, which changed the way indexes are created. This broke support of dropping columns of composite indexes for SQLite: due to limitations of ALTER in SQLite every time a column is dropped, we recreate the whole table without the given column; if a column is a part of a composite index, we change the index definition to omit that column and then indexes are recreated too. SQLAlchemy versions starting from 0.8 no more pay attention to 'columns' attribute of Index instances when generating DDL for indexes, so when one of columns of a composite index is dropped, we try to create a new index on the column that doesn't exist anymore, which of course fails. Closes-Bug: #1241038 Change-Id: I777b8ce36e36f49bfb0889908811a063cf1a527b
* Run tests on PostgreSQL and MySQL tooRoman Podolyaka2013-10-122-10/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | In addition to running tests with different Python and SQLAlchemy versions, they should also be run on different DB backends, which are used in production (PostgreSQL and MySQL). This patch: - modifies test_db.cfg to run tests on PostgreSQL and MySQL (Jenkins Slave credentials are used here, to ensure these tests are always run by Jenkins gate); if a backend is not available, test cases will be skipped for it - concurrency is set to 1 (sharing of the one MySQL or PostgreSQL DB among different test runner processes would lead to race conditions) - fixes tests dropping FK columns in MySQL: in earlier MySQL versions dropping a column that is a part of a FK constraint would lead to dropping of the FK too. As of MySQL 5.5 that's not the case anymore: if one tries to drop such column, he/she will get a very obscure error (something like "Error on rename of './openstack_citest/#sql-4af_aa2' to './openstack_citest/tmp_adddropcol' (errno: 150)") '\nALTER TABLE tmp_adddropcol DROP COLUMN r2'). So the solution if to drop FK constraints first, and only then the columns it is made up of Change-Id: I8c5d2874c83e7df46da69969ed54d85437c849e7
* decouple index name generation from sqlalchemy versionPádraig Brady2013-09-231-15/+19
| | | | | | | | | | In commit 0.7.2-16-gc670d1d the _index_identifier() implementation was copied from sqlalchemy, as that function was renamed in sqlalchemy 0.8. Instead handle call the renamed function when appropriate, to decouple ourselves from the sqlalchemy implementation. Change-Id: I97b22c20d96758fc5b6bd55318218edb26c5b5d0
* Fix exceptions for SQLAlchemy 0.8Pádraig Brady2013-07-111-2/+2
| | | | Change-Id: Ib541ac9d6b397300e34ca8b65aad459b612858c3
* added bugfixes for 0.8Josip Delic2013-07-111-0/+14
|
* Updated to OpenStack Build stuff.Monty Taylor2013-07-1115-162/+152
|
* fix error, Text columns have no widthJan Dittberner2013-02-091-1/+1
|
* fix deprecation warning by using MetaData.reflectJan Dittberner2013-02-094-6/+11
|
* Import correct exceptions module (Fixes issue 154).Alex Favaro2013-02-091-1/+1
|
* apply patch for issue #72 by asuffield@gmail.comasuffield@gmail.com2012-01-232-1/+11
| | | fixes #72
* Fix excludeTablesgetDiffOfModelAgainstModel is not passingJason Michalski2011-12-172-8/+24
| | | | | excludeTables correctly Fixes issue 140
* start next development iterationJan Dittberner2011-11-011-1/+1
|
* finalize changelog for 0.7.20.7.2Jan Dittberner2011-11-011-1/+1
|
* PEP-8 compliant script templatesJan Dittberner2011-10-292-4/+8
|
* add regression test (fixes issue 105)Jan Dittberner2011-10-281-0/+6
|
* fix issues with ConfigParser and existing repositories (fixes issue 115)Jan Dittberner2011-10-285-8/+11
|
* remove obsolete manage.py_tmpl (related to issue 121)Jan Dittberner2011-10-282-6/+0
|
* generate if __name__ == "__main__" in manage.py (fixes issue 121)Jan Dittberner2011-10-282-2/+5
|
* merge e5bd2821eea8 from https://code.google.com/r/alyazdi-patches/Jan Dittberner2011-10-281-1/+1
|\ | | | | (fixes issue 125)
| * Fix for issue #125, create the table on the same connection as the ALTER and ↵al.yazdi@gmail.com2011-10-261-1/+1
| | | | | | | | INSERT happen
* | merge fixes by wyenhoJan Dittberner2011-10-281-2/+3
|\ \
| * | fixed issue 129wyuenho@gmail.com2011-10-021-1/+1
| | |
| * | fixed issue 83wyuenho@gmail.com2011-10-021-1/+2
| |/
* | drop SQLAlchemy < 0.6 compatibility codeJan Dittberner2011-10-2814-200/+58
| |
* | fix SQLAlchemy 0.6.x compatibility of issue 128 patchJan Dittberner2011-10-281-1/+11
| |
* | fix issue 128: "table rename failure with sqlalchemy 0.7.x"markbmc@gmail.com2011-10-282-8/+10
| |
* | remove unused importDustin J. Mitchell2011-07-101-1/+0
| |
* | Fix issue 124: ignore sqlite_sequence in comparing db to modelDustin J. Mitchell2011-07-101-2/+10
|/
* Use two models in generated migrations. Test column addition and removal.Gabriel2011-07-073-51/+95
|
* Put constraints (positional) before args (keywords).Gabriel2011-07-051-1/+1
|
* Output has changed even without the SQLa patch, update #122 tests.Gabriel2011-07-051-1/+1
|
* Fix and test issue 118. Clarify genmodel transformations.Gabriel2011-07-056-99/+159
|
* Fix column creation in make_update_script_for_model.Gabriel2011-07-041-15/+14
| | | | | | | | | | Generating the script needs internal API updates: https://code.google.com/p/sqlalchemy-migrate/issues/detail?id=113 Getting the script to run needs the new columns defined: https://code.google.com/p/sqlalchemy-migrate/issues/detail?id=123 Table metadata represents the former state and does not contain the columns being added.
* More concise declarative output.Gabriel2011-06-291-18/+11
| | | https://code.google.com/p/sqlalchemy-migrate/issues/detail?id=122
* More pep8 compliant declarative output.Gabriel2011-06-291-7/+8
| | | https://code.google.com/p/sqlalchemy-migrate/issues/detail?id=122
* Fix some tests that broke when adding descriptions for sql scriptsPete Keen2011-06-125-16/+19
|
* Allow descriptions in sql change script filenamesPete Keen2011-06-104-16/+30
|
* Optionally number versions with timestamps instead of sequencesPete Keen2011-06-104-2/+46
|
* start next development iterationJan Dittberner2011-05-271-1/+1
|
* set migrate.__version__ to 0.7.1Jan Dittberner2011-05-271-1/+1
|
* fix column.create() properlyJan Dittberner2011-05-272-3/+4
|
* add migrate.__version__ (Fixes issue 111)Jan Dittberner2011-05-272-0/+13
| | | | | - add __version__ to migrate/__init__.py - add test in migrate/tests/__init__.py - update docs/changelog.rst
* no special treatment for SQLA 0.7 required in migrate.changeset.ansisqlJan Dittberner2011-05-271-8/+4
|
* remove commented codeJan Dittberner2011-05-261-5/+0
|
View Lorry Controller Status