)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"24c4496dd349827fb3f9131e634082eb46b8839d","unresolved":false,"context_lines":[{"line_number":15,"context_line":"This is completely unnecessary complexity and brancing"},{"line_number":16,"context_line":"in our codebase because the \u0027col IN items\u0027 statement is"},{"line_number":17,"context_line":"just a nice syntax offered by SQL that gets converted into"},{"line_number":18,"context_line":"\u0027col\u003d\u003ditem1 OR col\u003d\u003ditem2 OR col\u003d\u003ditem3...\u0027 statements"},{"line_number":19,"context_line":"under the hood. So in the case of one item, \u0027WHERE col IN \"F\"\u0027"},{"line_number":20,"context_line":"is the same as \u0027WHERE col \u003d \"F\"\u0027."},{"line_number":21,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"1a6ced46_60550ff9","line":18,"updated":"2015-03-26 06:23:21.000000000","message":"the corresponding sql operator is \u0027\u003d\u0027, not \u0027\u003d\u003d\u0027.","commit_id":"0e8f7e1712b2bd92725622568b99901e0bcda59a"},{"author":{"_account_id":6854,"name":"YAMAMOTO Takashi","email":"yamamoto@midokura.com","username":"yamamoto"},"change_message_id":"24c4496dd349827fb3f9131e634082eb46b8839d","unresolved":false,"context_lines":[{"line_number":16,"context_line":"in our codebase because the \u0027col IN items\u0027 statement is"},{"line_number":17,"context_line":"just a nice syntax offered by SQL that gets converted into"},{"line_number":18,"context_line":"\u0027col\u003d\u003ditem1 OR col\u003d\u003ditem2 OR col\u003d\u003ditem3...\u0027 statements"},{"line_number":19,"context_line":"under the hood. So in the case of one item, \u0027WHERE col IN \"F\"\u0027"},{"line_number":20,"context_line":"is the same as \u0027WHERE col \u003d \"F\"\u0027."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Change-Id: I8bee8c49d72958f5ae424f87c9dc98b8abe6f579"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"1a6ced46_80712baa","line":19,"updated":"2015-03-26 06:23:21.000000000","message":"WHERE col IN (\"F\")","commit_id":"0e8f7e1712b2bd92725622568b99901e0bcda59a"},{"author":{"_account_id":7787,"name":"Kevin Benton","email":"kevin@benton.pub","username":"blak111"},"change_message_id":"a7090aef243ffa2685531c5903570ac166297a64","unresolved":false,"context_lines":[{"line_number":16,"context_line":"in our codebase because the \u0027col IN items\u0027 statement is"},{"line_number":17,"context_line":"just a nice syntax offered by SQL that gets converted into"},{"line_number":18,"context_line":"\u0027col\u003d\u003ditem1 OR col\u003d\u003ditem2 OR col\u003d\u003ditem3...\u0027 statements"},{"line_number":19,"context_line":"under the hood. So in the case of one item, \u0027WHERE col IN \"F\"\u0027"},{"line_number":20,"context_line":"is the same as \u0027WHERE col \u003d \"F\"\u0027."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Change-Id: I8bee8c49d72958f5ae424f87c9dc98b8abe6f579"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"da9b358b_5db658dd","line":19,"in_reply_to":"1a6ced46_80712baa","updated":"2015-03-30 09:38:00.000000000","message":"I\u0027ll update the syntax if I need to re-upload for anything else. I think people will probably understand what I mean with the current one. :)","commit_id":"0e8f7e1712b2bd92725622568b99901e0bcda59a"}]}