)]}'
{"nova/db/sqlalchemy/migrate_repo/versions/144_add_node_to_migrations.py":[{"author":{"_account_id":100,"name":"Johannes Erdfelt","email":"johannes@erdfelt.com","username":"johannes.erdfelt"},"change_message_id":"e58992e22c0eb1064b93f187ec87b232cc46b12d","unresolved":false,"context_lines":[{"line_number":36,"context_line":"        raise Exception(\"Index \u0027%s\u0027 not found!\" % idx_name)"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"    idx.drop(engine)"},{"line_number":39,"context_line":"    table.indexes.remove(idx)"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"def upgrade(migrate_engine):"}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAAM3%2F%2BrFM%3D","line":39,"updated":"2013-02-21 23:51:12.000000000","message":"If this is a bug in SQLAlchemy, will a future update that fixes that bug cause this code to fail? (ie ValueError exception in the .remove() call)\n\nI guess not since we\u0027ve pinned SQLAlchemy to 0.7.8 or 0.7.9.\n\nJust trying to figure out the future impact of workarounds like this.","commit_id":"e9d893a69cfdc6af8ec9a06bbd94ca6fed1eb09c"},{"author":{"_account_id":475,"name":"Rick Harris","email":"rick.harris@rackspace.com","username":"rconradharris"},"change_message_id":"7f8cfda6f9b2690b182aecf8aa96238dd56efb5d","unresolved":false,"context_lines":[{"line_number":36,"context_line":"        raise Exception(\"Index \u0027%s\u0027 not found!\" % idx_name)"},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"    idx.drop(engine)"},{"line_number":39,"context_line":"    table.indexes.remove(idx)"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"def upgrade(migrate_engine):"}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAAM3%2F%2BrDM%3D","line":39,"in_reply_to":"AAAAM3%2F%2BrFM%3D","updated":"2013-02-22 00:01:47.000000000","message":"This \u0027probably\u0027 is a bug in SQLAlchemy, but I\u0027m not positive of that at the moment.\n\nI\u0027m planning to write a separate SQLAlchemy only test-case, and if so, try to get a patch upstream.\n\nIf that turns out to be the case, I\u0027ll come back here and add a FIXME.\n\nThat said, anything upstream is gonna take a while, so I think we should try to merge this ASAP so the migration at least works in the interim.","commit_id":"e9d893a69cfdc6af8ec9a06bbd94ca6fed1eb09c"}]}