change where the transaction is bound to
change where the transaction is bound to

this affects the where clause of the sql to fix the max for the next build number

i don't know why this is happening, but it is replicatable in the console

final-ci/travis-core,final-ci/travis-core,Tiger66639/travis-core,developerfm/travis-core,kidaa/travis-core,kidaa/travis-core,developerfm/travis-core,kidaa/travis-core,developerfm/travis-core,travis-ci/travis-core,final-ci/travis-core,Tiger66639/travis-core,GistIcon/travis-core,Tiger66639/travis-core,jantman/travis-core,travis-ci/travis-core,GistIcon/travis-core,GistIcon/travis-core,travis-ci/travis-core,jantman/travis-core