AI & keys
Generating and removing mock data
Fill a table with realistic AI-generated rows, see them tinted amber, and remove them in one click when you are done.
Mock rows are generated from your real schema so they respect types and constraints. They are tracked by primary key and tinted amber in the results grid so you never confuse them with production data.
Cleaning up
AddisDB keeps a ledger of every mock row it inserted. Open the mock-data panel and choose Remove mock data to delete exactly those rows — nothing else is touched.
Which databases it works on
Mock data works on PostgreSQL and everything on its wire, the MySQL family, SQL Server, SQLite, DuckDB and Oracle; on MongoDB, Cassandra and ScyllaDB, Neo4j and Memgraph, Elasticsearch and OpenSearch, Couchbase and DynamoDB; and on ClickHouse, Snowflake, BigQuery, Databricks, Trino, Presto, Dremio and Hive.
Schemaless engines are generated into whole rather than projected onto one sampled document, so a nested field is never quietly dropped — and where the engine assigns no key, AddisDB chooses one itself so the batch stays removable. Redis is the exception: it has no tables to generate into.