{"push_id":725593991,"size":1,"distinct_size":1,"ref":"refs/heads/suguwork","head":"b25527db037eaf1391943fb42bee67e70bcb1d65","before":"ad37d78d058e4997a375cf85ff45c3e407271e55","commits":[{"sha":"b25527db037eaf1391943fb42bee67e70bcb1d65","author":{"email":"0ee711480472e44bb0ec6060537f82d554add06e@google.com","name":"Sugu Sougoumarane"},"message":"vtgate batch API: Add AsTransaction flag\n\nBatch requests in vttablet currently allow \"begin\" and \"commit\"\nstatements. They were treated as special cases where vttablet would\nstart a transaction if such statements were seen.\nInitially, this looked flexible, but I realize that this has drawbacks.\nFor example, someone could issue a begin without a commit, or one could\nissue begin inside begin, or a begin-commit-begin, or a \"bEgIn\", etc.\nChecking for all these corner cases complicates the logic, and does not\nadd much value to the app.\nThis change adds an AsTransaction flag to the VTGate Batch\nrequests. If it's true, then the entire batch is executed in a\ntransaction. Otherwise, the statements are executed loosely.\nConsequently, I'll be outlawing begin and commit as valid statements\ninside batch requests.\nThe next change will be for vttablet.","distinct":true,"url":"https://api.github.com/repos/youtube/vitess/commits/b25527db037eaf1391943fb42bee67e70bcb1d65"}]}