1. 05 Jul, 2015 1 commit
    • Matt Riedemann's avatar
      Update flake8 related dependencies · dc07f8de
      Matt Riedemann authored
      In order to raise the cap on pbr we need to update
      the dependent versions of the flake8 related packages
      for the pep8 job since they have capped pbr.
      
      A couple of simple hacking issues are fixed, the rest
      are ignored.
      
      Change-Id: Icddb5bf284da7b6463ebcfc7512726149ffe6085
      dc07f8de
  2. 04 Jul, 2015 2 commits
  3. 02 Jul, 2015 1 commit
    • Sean Dague's avatar
      uncap pbr and sqla requirements · 35832555
      Sean Dague authored
      The cap of pbr causes issues now that pbr 1.2 is basically needed for
      a lot of projects to do the right thing with requirements ranges. The
      sqla capping is preventing new versions of sqla to be used in the
      OpenStack gates, and shouldn't be capped by a library.
      
      Change-Id: I5fc142eb8c9d616db2ed9b2f3e4e4d1147e131ff
      35832555
  4. 01 Jul, 2015 2 commits
    • Mike Bayer's avatar
      Update tests and reqs for SQLA 1.0 · a94dae7a
      Mike Bayer authored
      Lift the requirements to support SQLAlchemy 1.0.  Two tests
      were calling upon revised APIs and required adjustment.
      
      Change-Id: Ic91a91bb3c915027b522eace302f2ed074233294
      a94dae7a
    • Mike Bayer's avatar
      Ignore stderr output when invoking migrate script in tests · b8def7cb
      Mike Bayer authored
      Under Python 2.6 a setuptools warning is produced when
      the migrate runner runs.  Since migrate invokes its own
      commandline client from tests in a separate shell, the
      fixture we're using to do that must be told not to complain
      about this stderr.
      
      Change-Id: Ib5823754d6ffabe954665f2a7529ed0e56591ebf
      b8def7cb
  5. 17 Apr, 2015 1 commit
    • Victor Stinner's avatar
      Add Python 3 classifiers · d651f123
      Victor Stinner authored
      sqlachemy-migrate works on Python 3.3 and Python 3.4: announce it in
      classifiers in setup.cfg.
      
      Change-Id: Ibb2a803941dcc7b05efd407692b3627203ba2afe
      d651f123
  6. 16 Mar, 2015 1 commit
    • Qin Zhao's avatar
      Fix ibmdb2 index name handling · e57ee4c3
      Qin Zhao authored
      The ibmdb2 code calls _index_identifier() when it handles index name. This
      method only exists from sqlalchemy 0.6.5 to 0.7.*. Nova code change
      https://review.openstack.org/#/c/153123/ attempts to drop a db constraint and
      it fails to sync nova db with sqlalchemy 0.9.8 running against db2. Need to let
      ibmdb2 code identify sqlalchemy version and call the correct method to handle
      index name.
      
      Closes-Bug: 1428477
      
      Change-Id: Ie6333f9cea0209c1ea290356873a1a1bcf409bed
      e57ee4c3
  7. 24 Feb, 2015 3 commits
  8. 23 Feb, 2015 1 commit
  9. 22 Feb, 2015 1 commit
  10. 20 Feb, 2015 2 commits
    • Matt Riedemann's avatar
      Fix .gitignore for .tox and .testrepository · 9d212e6f
      Matt Riedemann authored
      The entries for tox and testrepository weren't
      working with `git clean -df` so this updates them
      to match what's in nova's .gitignore. Testing
      manually shows this doesn't blast those directories
      when running git clean.
      
      Change-Id: Iba569afabea748369f76351bf5521ca1c0fdce0c
      Closes-Bug: #1423983
      9d212e6f
    • Matt Riedemann's avatar
      allow dropping fkeys with sqlite · ae64d828
      Matt Riedemann authored
      This implements the ability to drop foreign keys
      with sqlite. It's basically the same implementation
      used for dropping unique constraints so the common
      code is refactored.
      
      The existing FKey test that was skipping sqlite is
      no longer skipped to show this works.
      
      Change-Id: Idaaf4229e34af4c21c3bcead4b4e22491d24238e
      Closes-Bug: #1423955
      ae64d828
  11. 29 Jan, 2015 1 commit
    • Mike Bayer's avatar
      Add pretty_tox setup · 997855db
      Mike Bayer authored
      This changeset adds the pretty_tox script runner to SQLAlchemy-migrate,
      so that current test runs can be viewed clearly.
      
      Change-Id: I3884703e24cb636983a0202c46899c772419d401
      997855db
  12. 27 Jan, 2015 1 commit
  13. 15 Jan, 2015 3 commits
  14. 14 Jan, 2015 1 commit
    • Ihar Hrachyshka's avatar
      script: strip comments in SQL statements · b9caaae4
      Ihar Hrachyshka authored
      Regular expression does not match correctly against statements that contain
      comments at their start. So strip those comments first (and whitespaces, while
      we are at it).
      
      Change-Id: Iad9b544bf995374d76cab1e125658aae2f8511f4
      Closes-Bug: #1410494
      b9caaae4
  15. 13 Jan, 2015 1 commit
    • Monty Taylor's avatar
      Remove svn version tag setting · b011e6cb
      Monty Taylor authored
      This is confusing our poor friend setuptools into appending a post0 on
      to release versions.
      
      Change-Id: I59a763f00f47d9a2fb0d26428a41fee82deff49d
      b011e6cb
  16. 11 Jan, 2015 1 commit
  17. 10 Jan, 2015 1 commit
  18. 09 Jan, 2015 2 commits
    • Ihar Hrachyshka's avatar
      Ignore transaction management statements in SQL scripts · 938757e7
      Ihar Hrachyshka authored
      Now that we don't run SQL script with a single .execute() call,
      transaction management statements (BEGIN, COMMIT, END) fail with
      operational error. Ignore them if occurred in a script.
      
      All in all, transactions are managed by SQLAlchemy-migrate itself, so
      there is no reason for the calling code to pass those statements in a
      SQL script. Warn user about the statements that are ignored.
      
      The ideal response to such a warning from library users is removing
      those redundant transaction management statements from their scripts.
      
      Note: ROLLBACK is not ignored even though it's one of transaction
      management statements because its usage in migration scripts is insane
      anyway, and we're better fail on it and not (almost) silently ignore it.
      
      Change-Id: Ie4179c0e9341d42656d66821aaac23f8dcd33927
      Closes-bug: 1368391
      938757e7
    • Rahul Priyadarshi's avatar
      Use native sqlalchemy 0.9 quote attribute with ibmdb2 · 74553f42
      Rahul Priyadarshi authored
      Commit 8d6ce64c started using the native
      quote attribute built into sqlalchemy 0.9 but missed the changes to the
      ibmdb2 changeset, so alter table statements fail for DB2 on sqlalchemy
      >= 0.9 (tested against 0.9.8).
      
      This fixes the same issue for the ibmdb2 changeset.
      
      Change-Id: Ia3fa6c3090b5eab29ed7746f4795d502990b8a2f
      74553f42
  19. 08 Jan, 2015 1 commit
    • Brant Knudson's avatar
      Don't add warnings filter on import · 244c6c55
      Brant Knudson authored
      The changeset module was adding a warnings filter on import. This
      affects all applications that wind up importing it. A library
      shouldn't modify the warnings filters unless asked.
      
      Closes-Bug: #1407736
      Change-Id: I893f8be48efd3d3642e977ab587c9e6dc867258b
      244c6c55
  20. 30 Oct, 2014 1 commit
  21. 10 Oct, 2014 1 commit
  22. 12 Sep, 2014 1 commit
  23. 03 Sep, 2014 1 commit
  24. 23 Aug, 2014 4 commits
    • Ihar Hrachyshka's avatar
      pep8: mark all pep8 checks that currently fail as ignored · 30f6aeab
      Ihar Hrachyshka authored
      Change-Id: Ic1dfb51598b920611acb1a0e437a32c5af90beda
      30f6aeab
    • Ihar Hrachyshka's avatar
      SqlScript: execute multiple statements one by one · 93ae2100
      Ihar Hrachyshka authored
      Some drivers [f.e. MySQL Connector] do not like multiple statements
      being passed to .execute(). They require either passing multi=True
      parameter to .execute() that is not DB-API 2.0 defined, or executing
      those statements one by one.
      
      For that patch, I've chosen the second option to stay away from driver
      specific hacks.
      
      Also removed SQLite hack that seems to be related to the same multiple
      statements issue.
      
      blueprint enable-mysql-connector
      
      Change-Id: Ic6d53ed1fef8aee9471f3540f06b39cd5ee4ef82
      93ae2100
    • Ihar Hrachyshka's avatar
      Make sure we don't throw away exception on SQL script failure · be1dd673
      Ihar Hrachyshka authored
      If SQL script failed, we don't currently log the failure anywhere, so
      users have hard time debugging an issue, if anything arises.
      
      Let's log the failure before proceeding with rollback.
      
      Change-Id: Ic92b1403c00bb238a68265a15150a4be6f6b2346
      be1dd673
    • Ihar Hrachyshka's avatar
      Pin testtools to < 0.9.36 · feb0c15a
      Ihar Hrachyshka authored
      New testtools require that setUp() and tearDown() are not called twice,
      while test_schema is built around multiple calls. So pinning the version
      for now until a proper fix is implemented.
      
      Closes-Bug: 1360252
      Change-Id: I184db35242d036dacc7933c1d762cccc7f5c40bb
      feb0c15a
  25. 04 Aug, 2014 1 commit
  26. 02 Aug, 2014 1 commit
    • Peter Conerly's avatar
      Fixes the auto-generated manage.py · 5542e1c5
      Peter Conerly authored
      Removes `six` from the locals().copy() so that it won't be templated into
      manage.py.  Currently manage.py is mis-templated and is failing.
      
      Change-Id: Ib3b7c7caac998fbaa45c3370547c9b8bf13abe41
      Closes-Bug: 171
      5542e1c5
  27. 22 Jul, 2014 1 commit
  28. 05 May, 2014 1 commit
  29. 16 Apr, 2014 1 commit
    • Matt Riedemann's avatar
      Move patch from oslo to drop unique constraints with sqlite · 93efb62f
      Matt Riedemann authored
      oslo-incubator commit 3f503faac for making sqlite work with dropping
      unique constraints in database migrations. This was made in
      oslo-incubator since at the time sqlalchemy-migrate was not in
      stackforge. Now that we can update sqlalchemy-migrate, move the patch
      over from oslo.
      
      This change also adds the support for the case that a unique constraint
      is dropped because the column it's on is dropped.
      
      Note that there are already unit tests that cover dropping a unique
      constraint directly and implicitly via dropping a column that is in
      the unique constraint.
      
      Related-Bug: #1307266
      
      Change-Id: I5ee8082a83aebf66f6e1dacb093ed79e13f73f5e
      93efb62f