This int ain't big enough for the both of us
Just got bug assigned to me, it's about automatically setting an index value in an integer (very important) database field. The suggestion on how to fix it is simply amazing:
"Set the correct value. To avoid collisions with any indices generated by the table sequence, start at IntMax+1"
With any luck, IntMax+1 will overflow silently to -IntMax-1 and assuming the table sequence started at 0 you'll be collision-free for the next IntMax-1 inserts.
Turns out the value is a BigInt, JimLahey commits suicide when he finds out.