{"push_id":635366834,"size":1,"distinct_size":1,"ref":"refs/heads/bug/1444209","head":"a9bcc6ec48ff6d6a7e7786287ac31ef9645bc100","before":"eae479d2678035301a2010e6af67734745915662","commits":[{"sha":"a9bcc6ec48ff6d6a7e7786287ac31ef9645bc100","author":{"email":"996ae66dd835d197b41888d714feef814ef0dc9e@redhat.com","name":"Michael McCune"},"message":"[WIP] Adding MySQL fixes to migrations\n\nThis change adds general fixes need for MySQL to perform the migrations\nfrom stable/juno to kilo. For MySQL, the Alembic documentation\nrecommends adding the type to all drop_constraints calls, additionally\nit is needed for alter_column as well. There is also an issue with MySQL\nnot allowing some alter_column changes on columns that have foreign key\nconstraints.\n\nChanges\n* correcting alter_column and drop_constraints in 795737bb3c3\n* correcting alter_column in 256da65e0c5f\n* correcting drop_constraints and associated behavior in 1c0f328bfce0\n* adding names for the foreign constraints in ProjectSecret\n\nChange-Id: I558e5dca5d9c99150f2dceb251235e0d0a2f5a16\nCloses-Bug: 1444209","distinct":true,"url":"https://api.github.com/repos/elmiko/barbican/commits/a9bcc6ec48ff6d6a7e7786287ac31ef9645bc100"}]}