Show HN: DDL to Data – Generate realistic test data from SQL schemas
I built DDL to Data after repeatedly pushing back on "just use production data and mask it" requests. Teams needed populated databases for testing, but pulling prod meant security reviews, PII scrubbing, and DevOps tickets. Hand-written seed scripts were the alternative slow, fragile, and out of sync the moment schemas changed.
Paste your CREATE TABLE statements, get realistic test data back. It parses your schema, preserves foreign key relationships, and generates data that looks real, emails look like emails, timestamps are reasonable, uniqueness constraints are honored.
No setup, no config. Works with PostgreSQL and MySQL.
Would love feedback from anyone who deals with test data or staging environments. What's missing?
12 comments
[ 2.4 ms ] story [ 35.5 ms ] threadThe pricing seems extremely high for what's basically a call to https://github.com/faker-ruby/faker but that makes sense if it has to pay for OpenAI tokens.
(who knows though, plenty of B2B deals signed for sillier things than this - good luck, OP)
I've written seed data scripts a number of times, so I get the need. How do you think about creating larger amounts of data?
E.g., I'm building a statistical product where the seed data needs to be 1M rows; performance differences between implementations start to matter.
I like the concept but the painpoint has never been around creating realistic looking emails and such like, but creating data that is realistic in terms of the business domain and in terms of volume.
I also provide an option to select how to generate data for specific fields.
https://fakemydb.alles-tools.com
UI is a bit clunky - will revamp it :)
Developers use their tool or develop a script (with ai or not)
We made it free, the value comes when you can use it in your development process.
https://www.tabulify.com/learning-tabulify-step-9-how-to-fil...
The cost of calling a service is also not free.
In all case, all the best in your endeavour.