)]}'
{"oslo_db/sqlalchemy/models.py":[{"author":{"_account_id":6849,"name":"Roman Podoliaka","email":"roman.podoliaka@gmail.com","username":"rpodolyaka"},"change_message_id":"86f3ffd8165dba105bcd8b65fd2f3246a36cc546","unresolved":false,"context_lines":[{"line_number":114,"context_line":""},{"line_number":115,"context_line":"class TimestampMixin(object):"},{"line_number":116,"context_line":"    created_at \u003d Column(DateTime, default\u003dlambda: timeutils.utcnow())"},{"line_number":117,"context_line":"    updated_at \u003d Column(DateTime, default\u003dlambda: timeutils.utcnow(),"},{"line_number":118,"context_line":"                        onupdate\u003dlambda: timeutils.utcnow())"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"7a016987_701fa06c","line":117,"updated":"2015-05-19 09:36:50.000000000","message":"Personally, I\u0027m against changing this, as this effectively changes the existing semantics of `updated_at`: it\u0027s meant to remain NULL until the row has been modified for the first time.\n\nOf course, we could implement checks like \"if this row has ever been modifed?\" by comparing created_at/updated_at, by why do that, if it works as it is?","commit_id":"52e84848cd7826c9389ba75f9ff00655f24d454c"}]}
