{"push_id":929296511,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"bdffb5ef461dd845279d05c8c7a16a049122a72e","before":"57edf1e37c2a405b279cb656f8f0799ce3473b8e","commits":[{"sha":"c711a53bb205d3bbedcf116d4fd0412614168724","author":{"email":"b960b14c160e552c7c192a2eecd6c103ae4d8a42@gmail.com","name":"Chris Bannister"},"message":"correctly handle tuples in MapScan\n\nTuples are handled specially in Scan and as such each element in the\ntuple must be treated as a single column. MapScan now generates one\nelement in the map for each element in the tuple, these can be accessed\nby name using the new TupleColumnName function.\n\nfixes #561","distinct":true,"url":"https://api.github.com/repos/gocql/gocql/commits/c711a53bb205d3bbedcf116d4fd0412614168724"},{"sha":"f11cb55c32a28a4f1ebe52c3883e1f05559e85dd","author":{"email":"b960b14c160e552c7c192a2eecd6c103ae4d8a42@gmail.com","name":"Chris Bannister"},"message":"err count missmatched is now improved","distinct":true,"url":"https://api.github.com/repos/gocql/gocql/commits/f11cb55c32a28a4f1ebe52c3883e1f05559e85dd"},{"sha":"bdffb5ef461dd845279d05c8c7a16a049122a72e","author":{"email":"b960b14c160e552c7c192a2eecd6c103ae4d8a42@gmail.com","name":"Chris Bannister"},"message":"Merge pull request #563 from Zariel/tuple-nested-types\n\ncorrectly handle tuples in MapScan","distinct":true,"url":"https://api.github.com/repos/gocql/gocql/commits/bdffb5ef461dd845279d05c8c7a16a049122a72e"}]}