{"push_id":1327141958,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"7453c4ff2caa54a7de7f69bb8b2e4802b502761d","before":"8a522e4bf66c5197e0959914751557f4919e7662","commits":[{"sha":"7453c4ff2caa54a7de7f69bb8b2e4802b502761d","author":{"name":"Phil Davis","email":"d10d92d1ccfeef7a6a6fe8b3d078e129ceb891cc@inf.org"},"message":"Corrections to min and max selection\n\nIn the Travis docker image, the queries that combined the selection of a\nTemperature record with the selection of a group statistic (min, max or\ncount) were causing problems.\nfiltered.first() was always returning just the last Temperature record\nin the set (which happens to be the one with the biggest timestamp),\nalong with the statistic(s) (count, min and/or max value).\nI have separated out the queries so that the queries for an actual\nTemperature record are done for just that, with order_by() to get the\nmin or max record at the front of the list.\nNow it works fine on Travis, and I also tried a few queries manually in\nmy Ubuntu VM and they are working fine.\nActually I don't understand how it was working for us on the RPi, must\nhave been something special in the way the \"mixed\" queries happened.\nThe test spec is enhanced to check all the expected min and max from the\ntest cases.","distinct":true,"url":"https://api.github.com/repos/swalladge/rpi-temperature-server/commits/7453c4ff2caa54a7de7f69bb8b2e4802b502761d"}]}
{"actor":{"display_login":"phil-davis"}}