{"push_id":621674093,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"c39b64d963db7142635f3b33d0339fd0cfae2dc2","before":"2ecdbbec10bf3d81faa666797f32ee335b6c8d3b","commits":[{"sha":"c39b64d963db7142635f3b33d0339fd0cfae2dc2","author":{"email":"46f1a0bd5592a2f9244ca321b129902a06b53e03@epriestley.com","name":"epriestley"},"message":"Improve handle loading semantics for tokenizers\n\nSummary:\nRef T7689. Fixes T7688. When there are a bunch of tokenizers with different values of the same object type (e.g. 5 tokenizers with users a, b, c, d, e) we currently issue 5 separate queries to load their handles.\n\nImprove this behavior in the common case so we can usually batch these loads.\n\nTest Plan:\n  - In Maniphest, set the various search fields to different values.\n  - Used DarkConsole to examine query plan.\n  - Saw fewer queries after patch than before.\n\nReviewers: btrahan\n\nReviewed By: btrahan\n\nSubscribers: epriestley\n\nManiphest Tasks: T7688, T7689\n\nDifferential Revision: https://secure.phabricator.com/D12261","distinct":true,"url":"https://api.github.com/repos/phacility/phabricator/commits/c39b64d963db7142635f3b33d0339fd0cfae2dc2"}]}