{"push_id":638845435,"size":1,"distinct_size":0,"ref":"refs/heads/master","head":"3e80d628bd133d0fd0687e35b8d13abd1d31d6df","before":"2c91f71776006968c091b683ea5f187dfaca72df","commits":[{"sha":"3e80d628bd133d0fd0687e35b8d13abd1d31d6df","author":{"email":"bb10354a889e9c8a6c713f2ff3dd3581d4bb27e4@zzzcomputing.com","name":"Mike Bayer"},"message":"- Fixed issue where a straight SELECT EXISTS query would fail to\nassign the proper result type of Boolean to the result mapping, and\ninstead would leak column types from within the query into the\nresult map.  This issue exists in 0.9 and earlier as well, however\nhas less of an impact in those versions.  In 1.0, due to #918\nthis becomes a regression in that we now rely upon the result mapping\nto be very accurate, else we can assign result-type processors to\nthe wrong column.   In all versions, this issue also has the effect\nthat a simple EXISTS will not apply the Boolean type handler, leading\nto simple 1/0 values for backends without native boolean instead of\nTrue/False.   The fix includes that an EXISTS columns argument\nwill be anon-labeled like other column expressions; a similar fix is\nimplemented for pure-boolean expressions like ``not_(True())``.\nfixes #3372","distinct":false,"url":"https://api.github.com/repos/zzzeek/sqlalchemy/commits/3e80d628bd133d0fd0687e35b8d13abd1d31d6df"}]}