computing, dbs, work shit
i went to put a unique index on the table i'm testing and it failed
it was on four columns, one of which contains a UUID so i was surprised, even though the table had over 20M rows it seemed pretty unlikely to happen
realized after truncating the table and trying from scratch that...
because i populate the db in 10 subprocesses and i'm... lazy... all subprocesses had identical copies of the data generator, with the same seed
so i force them to re-seed now and it ok!
computing, dbs, work shit
@bea what, that's incredible
Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.
While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.
Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!
computing, dbs, work shit
@vahnj lol yes, my db had 10 copies of everything haha
fortunately faker has separate functions for forcing seeding of the shared RNG as well as forcing generators to use their own RNG and seed that, so i did the start of the worker code