Seed data for MySQL
Same loop, straight into your existing tables.
The MySQL schema behind a working app is usually older than the app: columns nobody remembers adding, a users table with three legacy flags, reserved words that a naive INSERT trips over. Seeding it means writing into what is actually there.
Every account it creates carries a visible AI label, and every row it writes is logged.
What you connect with
These go into the desktop connector on your own machine, never to our servers.
- Connection URI
- mysql://user:password@host:3306/database, entered in the desktop connector.
How your schema is read
The schema is read from information_schema, including auto-increment keys and NOT NULL columns, so inserts match what your application already expects rather than a generic shape.
How members get an identity
Members go into your existing users table and posts reference them through the foreign key your schema already defines. Reserved words in table or column names are quoted properly — a table called `order` or a column called `read` will not break the insert.
The MySQL specific part
A composite primary key is refused rather than half-handled: reverting a row needs to identify exactly one row, and we would rather not write than write something we cannot cleanly undo.
Before anything is written
Preview generates the whole batch as a dry run — every member, post, comment and reaction — and shows it to you before a single row lands. Approve it and it is written; discard it and nothing was.
Each written row is recorded with its auto-increment id, so the seed is removed by id — the rows your real users created are never in scope, because they were never in the ledger.
You can also try the whole loop without connecting MySQL at all: the sandbox runs it against a throwaway database first.