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