)]}'
{"neutron/db/migration/alembic_migrations/versions/ussuri/expand/c3e9d13c4367_add_binding_index_to_.py":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"2fa0cd360df14a804aa20d0971e1295bd456c5f7","unresolved":false,"context_lines":[{"line_number":39,"context_line":"    op.add_column(NETWORK_DHCP_AGENT_BINDING,"},{"line_number":40,"context_line":"                  sa.Column(\u0027binding_index\u0027, sa.Integer(), nullable\u003dFalse,"},{"line_number":41,"context_line":"                            server_default\u003d\u00271\u0027, primary_key\u003dTrue,"},{"line_number":42,"context_line":"                            autoincrement\u003dTrue))"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"    bindings_table \u003d sa.Table("},{"line_number":45,"context_line":"        NETWORK_DHCP_AGENT_BINDING,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3fa7e38b_a9296e9c","line":42,"updated":"2019-10-29 18:50:11.000000000","message":"I still have a question about this \"autoincrement\" parameter. The binding_index field will link a network with several agents. But this value should start, for each network, from 1.  Doing this, we\u0027ll have something like a \"id\" parameter with autoincrement. That information is irrevelant for the \"networkdhcpagentbindings\" register because we don\u0027t need an \"id\" field.","commit_id":"0c690306dbb133663ea8dc98988c7e8893234487"},{"author":{"_account_id":5948,"name":"Oleg Bondarev","email":"obondarev@mirantis.com","username":"obondarev"},"change_message_id":"24e8580d5f823531d00510608873cfec0c8599a4","unresolved":false,"context_lines":[{"line_number":39,"context_line":"    op.add_column(NETWORK_DHCP_AGENT_BINDING,"},{"line_number":40,"context_line":"                  sa.Column(\u0027binding_index\u0027, sa.Integer(), nullable\u003dFalse,"},{"line_number":41,"context_line":"                            server_default\u003d\u00271\u0027, primary_key\u003dTrue,"},{"line_number":42,"context_line":"                            autoincrement\u003dTrue))"},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"    bindings_table \u003d sa.Table("},{"line_number":45,"context_line":"        NETWORK_DHCP_AGENT_BINDING,"}],"source_content_type":"text/x-python","patch_set":1,"id":"3fa7e38b_f4f88f4a","line":42,"in_reply_to":"3fa7e38b_a9296e9c","updated":"2019-10-30 10:51:16.000000000","message":"Let me just delete it since \"SQLite does not support autoincrement for composite primary keys\" anyway. That would mean that we tolerate unique constraint violation when auto-scheduling networks during rolling upgrade (when some non-upgraded servers are running against upgraded DB)","commit_id":"0c690306dbb133663ea8dc98988c7e8893234487"}]}