)]}'
{"trove/guestagent/datastore/mysql/service.py":[{"author":{"_account_id":5293,"name":"Nikhil","email":"SlickNik@gmail.com","username":"slicknik"},"change_message_id":"31db18b501fbbdb36a2e41d3dc4b4b78e59e5ffa","unresolved":false,"context_lines":[{"line_number":53,"context_line":"MANAGER \u003d CONF.datastore_manager if CONF.datastore_manager else \u0027mysql\u0027"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"INCLUDE_MARKER_OPERATORS \u003d {"},{"line_number":56,"context_line":"    True: \"\u003d\","},{"line_number":57,"context_line":"    False: \"\u003e\""},{"line_number":58,"context_line":"}"},{"line_number":59,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_647752a0","line":56,"updated":"2014-12-19 10:10:42.000000000","message":"Please can we not change the meaning of \"INCLUDE_MARKER_OPERATORS\" -- it means specifically that the list of results returned should be \"\u003e\u003d\". If we need to make use of a strict \u003d operator, let\u0027s redefine this so that it makes sense in this new context.","commit_id":"a668ee473acee74db473bd3ea85e7b82c023c312"},{"author":{"_account_id":7806,"name":"Sushil Kumar","email":"skm.net@gmail.com","username":"sushilkm"},"change_message_id":"1cc56bdd6ada7a3eb420b7e95ed066073e3e5936","unresolved":false,"context_lines":[{"line_number":53,"context_line":"MANAGER \u003d CONF.datastore_manager if CONF.datastore_manager else \u0027mysql\u0027"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"INCLUDE_MARKER_OPERATORS \u003d {"},{"line_number":56,"context_line":"    True: \"\u003d\","},{"line_number":57,"context_line":"    False: \"\u003e\""},{"line_number":58,"context_line":"}"},{"line_number":59,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3a961159_9d96e892","line":56,"in_reply_to":"3a961159_647752a0","updated":"2014-12-20 03:53:38.000000000","message":"I did not understood this one, like where is this specification and the meaning defined.\n\nThe reason, what prompted me to make this change was that \"include_marker\u003dTrue\" was only used for the specific search to find users or schemas, and in entire code-base there are 3 instances of this being used in https://github.com/openstack/trove/blob/master/trove/extensions/mysql/models.py\n\nat Line 87, 160, 296.\n\nSo that meant only when we were searching for the exact we needed this value to be True, but since this value True was resolving as \"\u003e\u003d\" there were multiple values being fetched resulting in the bug described.","commit_id":"a668ee473acee74db473bd3ea85e7b82c023c312"},{"author":{"_account_id":10215,"name":"Peter Stachowski","email":"peter@tesora.com","username":"peterstac"},"change_message_id":"a41998bed1d8988cf40e3aa004e96b49a5918914","unresolved":false,"context_lines":[{"line_number":53,"context_line":"MANAGER \u003d CONF.datastore_manager if CONF.datastore_manager else \u0027mysql\u0027"},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"INCLUDE_MARKER_OPERATORS \u003d {"},{"line_number":56,"context_line":"    True: \"\u003d\","},{"line_number":57,"context_line":"    False: \"\u003e\""},{"line_number":58,"context_line":"}"},{"line_number":59,"context_line":""}],"source_content_type":"text/x-python","patch_set":2,"id":"da9b358b_ed31deed","line":56,"updated":"2015-03-30 20:55:23.000000000","message":"This is used to determine whether the \u0027marker\u0027 record should be returned with the next set.  Typically this would be false (i.e. \u003e marker) so that the new list doesn\u0027t contain the last value from the previous list.  In the cases you cite, you\u0027re right, it\u0027s being used to return just one record (limit\u003d1) and so it uses include_marker\u003dtrue to make sure it\u0027s the marker record being found. This is a bit confusing in the code, I admit, but I agree that changing the meaning of the operator isn\u0027t the correct way to fix it.","commit_id":"0438e1a7fca69783cab346cf6d49746fa9b7c3b0"}]}
