Data Generation
Edit and Export
Refine generated data and export SQL, XML, JSON, or CSV.
Edit and Export
After an initial run, refine output and export in the format your workflow needs.
Edit Pass
Use edit mode to update mappings and regenerate data with improved realism, or ask the Data Assistant to change value profiles in plain language.
Good Reasons To Re-Edit
- Column values look too generic.
- Relationship values require stricter behavior.
- Edge-case coverage is missing.
Export Formats
- SQL: INSERT-ready data for relational workflows.
- JSON: application or fixture workflows.
- CSV: spreadsheet and import tooling.
- XML: integration and legacy system workflows.
Export Considerations
Hidden Columns
Hidden columns are excluded from output. You can also untick columns for a single export.
Insert Order
Tables are always exported parents first, whatever order you selected them in, so SQL imports satisfy foreign keys.
- MySQL and SQLite: SQL exports also switch foreign key checks off during the import.
- PostgreSQL: has no such switch, so the order is what makes the import succeed.
See Relationships and Integrity.
Format Selection
- Use SQL for direct DB seed workflows.
- Use JSON for API fixtures and app tests.
- Use CSV for analyst-friendly validation.
Download Flow
Exports are generated and delivered through signed download links.
Repeatable Workflow
- Run generation.
- Review sample rows (the Preview table picker is searchable).
- Edit mappings or ask the Data Assistant to adjust profiles.
- Regenerate.
- Export final data format.