What naming convention do the tables follow?

Tables use lowercase snake_case and are pluralized (users, order_items), which is the most widely recommended SQL convention. PostgreSQL and SQLite use it directly; MySQL also works well in lowercase to stay portable across operating systems.

Why are MySQL names lowercase?

MySQL table-name case sensitivity depends on the host filesystem, so lowercase names avoid cross-platform surprises. The generator keeps MySQL output lowercase for safe portability between Linux and macOS or Windows.

Does it generate a schema name too?

Yes for PostgreSQL, which supports named schemas like app or core. MySQL and SQLite do not use the same schema concept, so the generator labels the namespace as the database itself for those flavors.

Are the names valid SQL identifiers?

Yes. They use only lowercase letters, digits, and underscores and never start with a digit, so they need no quoting in standard SQL and stay readable in migrations and ORMs.

Can I use these directly in a Prisma or Rails schema?

Yes. The plural snake_case tables map cleanly to Rails conventions and to Prisma @@map directives, and the database name works as your connection target. Adjust pluralization if your ORM expects singular models.

Database Name Generator

What this tool does

The Database Name Generator suggests a complete naming set — a database name, a schema namespace, and several table names — that follows mainstream SQL conventions for the flavor you choose. Pick an application domain and a SQL engine and it returns consistent, valid identifiers you can drop straight into a migration.

How it works

Each domain has a curated pool of entity nouns (for example, e-commerce includes product, order, cart, payment). The generator builds a database name from the domain plus an environment-neutral suffix, derives a schema namespace (a named schema for PostgreSQL, or the database itself for MySQL and SQLite), and selects several entities to render as table names. Tables come out as lowercase, pluralized snake_case — the most portable and widely recommended convention. All identifiers use only [a-z0-9_] and never begin with a digit, so they are valid without quoting.

Everything is generated locally in your browser.

Tips and notes

Snake_case plural tables map cleanly to Rails and to Prisma @@map.
MySQL output stays lowercase to avoid filesystem case-sensitivity bugs.
For PostgreSQL you get a real named schema; for MySQL/SQLite the namespace is the database.
Re-roll to explore different entity sets for the same domain.