)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":7118,"name":"Ian Wienand","email":"iwienand@redhat.com","username":"iwienand"},"change_message_id":"89d4017fb23204ed47be776de2919202ad8d55ed","unresolved":false,"context_lines":[{"line_number":34,"context_line":"      Use latin1 character set when creating the nova database"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"So, update Nova database creation setup so that encoding is set to UTF-8 by"},{"line_number":37,"context_line":"default when using PostgreSQL."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Change-Id: I75ebc825db11948d48fc027ff1abf704ad9931a0"},{"line_number":40,"context_line":"Closes-bug: #1397078"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":7,"id":"3a961159_87b63589","line":37,"updated":"2014-12-08 00:56:50.000000000","message":"except this doesn\u0027t just do it for postgresql?  my understanding from Ib768402a9337c918309030a92ab81da17269f4f6 was that it was a performance issue for mysql","commit_id":"03fa0be7747360316d56f47aba291d3cbf6a3a15"},{"author":{"_account_id":6962,"name":"Kashyap Chamarthy","email":"kchamart@redhat.com","username":"kashyapc"},"change_message_id":"cba07de4df4544ef1eed4e22d98900848f6d39f9","unresolved":false,"context_lines":[{"line_number":34,"context_line":"      Use latin1 character set when creating the nova database"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"So, update Nova database creation setup so that encoding is set to UTF-8 by"},{"line_number":37,"context_line":"default when using PostgreSQL."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Change-Id: I75ebc825db11948d48fc027ff1abf704ad9931a0"},{"line_number":40,"context_line":"Closes-bug: #1397078"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":7,"id":"3a961159_e7cd3288","line":37,"in_reply_to":"3a961159_87b63589","updated":"2014-12-08 08:58:59.000000000","message":"For MySQL, anyway, the databases are UTF8 when you examine them once a successful DevStack instances. So, I don\u0027t think it\u0027s changing behaviour for MySQL.\n\nBut I\u0027ll admit, I haven\u0027t examined the said performance issues. \n\nAnd, looks like I made a duplicate patch as I wasn\u0027t aware of Ihar\u0027s above patch. Should I just abandon this?","commit_id":"03fa0be7747360316d56f47aba291d3cbf6a3a15"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"d9d0d8717038e985af09299846420d92fae3476d","unresolved":false,"context_lines":[{"line_number":34,"context_line":"      Use latin1 character set when creating the nova database"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"So, update Nova database creation setup so that encoding is set to UTF-8 by"},{"line_number":37,"context_line":"default when using PostgreSQL."},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Change-Id: I75ebc825db11948d48fc027ff1abf704ad9931a0"},{"line_number":40,"context_line":"Closes-bug: #1397078"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":7,"id":"3a961159_c7b036f7","line":37,"in_reply_to":"3a961159_87b63589","updated":"2014-12-08 08:58:06.000000000","message":"afaik the commit was to avoid non-InnoDB databases from wasting precious key chars (that were quite limited) to unicode.\n\nNow that we always use InnoDB, and now that we translate the whole database for nova and other projects to unicode during migrations anyway, we don\u0027t really need to set utf8 in the first place.\n\nThe performance impact could be due to us using unicode for all tables and fields in databases. It may indeed be there, though we *already* use unicode globally, so the proposed patch changes nothing in this regard.","commit_id":"03fa0be7747360316d56f47aba291d3cbf6a3a15"}]}
