Another important difference that I can see between clickhouse-obfuscator and datasino is that obfuscator takes a long way to make sure data, although anonimise

Another important difference that I can see between clickhouse-obfuscator and datasino is that obfuscator takes a long way to make sure data, although anonimised, remains statistically realistic, whereas datasino is a dumb data filler/fuzzer: the output values will just be random bits. It's OK if you care about the data structure only but not so much when you need more "realistic" data. Something I'd like to add to datasino is indeed a way to specify constraints on some fields, beside their type, so for instance a column that's supposed to store a time actually look like a time and not a random integer. I just haven't found a nice and simple way to specify those constraints yet.