)]}'
{"doc/source/devref/effective_neutron.rst":[{"author":{"_account_id":7016,"name":"Swaminathan Vasudevan","email":"swvasude@cisco.com","username":"souminathan"},"change_message_id":"f75559f7da8ae2511ecd0dbbb8e43352cc4682dd","unresolved":false,"context_lines":[{"line_number":121,"context_line":"* Conversely, do not use lazy\u003d\u0027joined\u0027 if the relationship is only used in"},{"line_number":122,"context_line":"  corner cases because the JOIN statement comes at a cost that may be"},{"line_number":123,"context_line":"  significant if the relationship contains many objects. For example, see"},{"line_number":124,"context_line":"  `this patch \u003chttps://review.openstack.org/#/c/168214/\u003e`__ which reduced a"},{"line_number":125,"context_line":"  subnet retrieval by ~90% by avoiding a join to the IP allocation table."},{"line_number":126,"context_line":"* When writing extensions to existing objects (e.g. Networks), ensure that"},{"line_number":127,"context_line":"  they are written in a way that the data on the object can be calculated"}],"source_content_type":"text/x-rst","patch_set":1,"id":"da6ed579_9dc893aa","line":124,"updated":"2016-01-15 21:05:51.000000000","message":"https://review.openstack.org/#/c/268297/ - There is a patch number refered in this patch which is not there in the #L124.\nDo we need it here?","commit_id":"167b5bac099e7acf43584c81cb16234aa7b6f0ae"}]}
