Closed GoogleCodeExporter closed 9 years ago
http://comments.gmane.org/gmane.comp.python.sqlalchemy.user/30027
Original comment by mattrie...@gmail.com
on 14 Jul 2014 at 2:44
>>>
2014-07-09 02:36:03.615 | 2014-07-09 10:36:03.612 27124 TRACE keystone File
"/usr/local/lib/python2.7/dist-packages/migrate/changeset/databases/ibmdb2.py",
line 268, in _visit_constraint
2014-07-09 02:36:03.615 | 2014-07-09 10:36:03.612 27124 TRACE keystone for
column in constraint.columns._all_cols:
<<<
above trace shows issue comes from sqlalchemy-migrate but similar issue also
have with ibm_db_sa, I have make some changes to resolve this and committed the
same in git branch.
I also have created a patch for sqlalchemy-migrate, you can find it in
attachment.
Please give a try and let me know how it goes.
Original comment by rahul.pr...@in.ibm.com
on 18 Jul 2014 at 9:36
Attachments:
Original comment by rahul.pr...@in.ibm.com
on 18 Jul 2014 at 9:50
Rahul, thanks, the sqlalchemy-migrate change is up for review here:
https://review.openstack.org/#/c/108129/
Original comment by mattrie...@gmail.com
on 18 Jul 2014 at 6:45
The sqlalchemy-migrate patch didn't work because constraint.columns doesn't
have a keys() method.
The updated patch is here: https://review.openstack.org/#/c/108129/4
UniqueConstraint inherits an __iter__ method which returns a tuple of the
Column objects in the constraint so I just used that.
Original comment by mattrie...@gmail.com
on 4 Aug 2014 at 2:38
I have tested the changes with SQLAlchemy-0.8.4 but with adding
UniqueConstraint. You are facing the issue with adding FK constraint.
I will check with FK Constraint and will let you know if I face same issue.
Original comment by rahul.pr...@in.ibm.com
on 6 Aug 2014 at 9:03
This is caused by adding FK constraint, It doesn't effect ibm_db_sa changes but
I have modified the changes for code cleanup.
Original comment by rahul.pr...@in.ibm.com
on 7 Aug 2014 at 8:39
@Rahul, OK, thanks for testing it out.
Original comment by mattrie...@gmail.com
on 7 Aug 2014 at 2:02
Code changes released with ibm_db_sa-0.3.2
Original comment by rahul.pr...@in.ibm.com
on 5 Nov 2014 at 6:33
Original issue reported on code.google.com by
mattrie...@gmail.com
on 11 Jul 2014 at 3:58