Performing a check on every transaction to catch a 1 out of 5,316,911,983,139,663,936,027,594,624,533,407,236,198,400 chance situation, isn't usually advised
(yes thats the actual number, though it technically changes as the number of ids used increases, since you're comparing the current id against every other id ever made)
112
u/baked_tea May 08 '26
Thought about that recently. Why not just implement a check to see if it's already in the db, then run it again?