Supported Formats
Legend
- ✅: Supported
- ⚡: Supported via workaround
- ⛔: Not in progress
- ⌛️: In progress
Below is a list of currently supported (or planned) formats and integrations.
- Web Support: Support status for the web version.
- CLI Support: Support status for the CLI version. ⚡ indicates support through workarounds (e.g., using pg_dump or tbls).
- Identifier: Used for specifying the format in the CLI (via
--format=postgresql) or as a web query parameter (e.g.,?format=schemarb).
| Technology | Web Support | CLI Support | Identifier |
|---|---|---|---|
| PostgreSQL | ✅ | ✅ | postgresql |
| Ruby on Rails | ✅ | ✅ | schemarb |
| Prisma | ✅ | ✅ | prisma |
| tbls | ✅ | ✅ | tbls |
| Drizzle | ✅ | ✅ | drizzle |
| MySQL | ⛔ | ⚡ | - |
| SQLite | ⛔ | ⚡ | - |
| BigQuery | ⛔ | ⚡ | - |
For CLI support marked with ⚡, you can use the following workarounds:
- Generate a PostgreSQL file using pg_dump (see instructions), then process it with the
postgresqlformat - Generate a schema.json using tbls (see instructions), then process it with the
tblsformat
Format Auto-Detection
Liam ERD automatically attempts to determine the schema format for both Web and CLI versions. The detection process works as follows:
- File Name Check: Filenames such as
schema.rborSchemafileare assumed to be inschemarbformat. - File Extension Check: Files ending in
.rbare treated asschemarb, while files ending in.sqlare treated aspostgresql. - For more details, refer to the
detectFormat.tsfile in our GitHub repository.
If the automatic detection does not match your desired format, you can specify it manually:
- Web: Use the
formatquery parameter (e.g.,?format=schemarb) - CLI: Use the
--formatoption (e.g.,--format=schemarb)
If there's another database schema or ORM you'd love to see supported, please let us know in the GitHub Discussions.