{"push_id":1285935875,"size":1,"distinct_size":1,"ref":"refs/heads/should_use_cache_improvements","head":"2ee8ed640d278f709ec37de278da1c4af93769ab","before":"fa005c3c59d3da11e5f2f6eec3120099ab5c4c14","commits":[{"sha":"2ee8ed640d278f709ec37de278da1c4af93769ab","author":{"name":"Eugene Kenny","email":"8498dc38041ae775eded89bd17ca900045d3e33e@gmail.com"},"message":"Allow cache reads inside unjoinable transactions\n\nAn unjoinable transaction forces any transactions nested inside it to\nbehave as if they were at the top level: after_commit callbacks for\nrecords modified during the nested transaction will be executed when it\ncommits, even though the updated data won't be visible to other\nconnections until the outer transaction has also committed.\n\nRails creates unjoinable transactions in two places: in the sandbox\nconsole, and around transactional tests. In both of these cases, the\nuser expects their code to behave as if the transaction wasn't there;\nwith this change, IdentityCache will conform to that expectation by only\ndisabling cache reads inside joinable transactions.\n\nIdentityCache currently never reads from the cache during transactional\ntests, since there is always at least one transaction open. With this\nchange transactional tests behave more like production code, which will\nhelp catch issues like updating a record that came from the cache.","distinct":true,"url":"https://api.github.com/repos/eugeneius/identity_cache/commits/2ee8ed640d278f709ec37de278da1c4af93769ab"}]}
{"actor":{"display_login":"eugeneius"}}