Skip to content

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update database page
Browse files Browse the repository at this point in the history
droserasprout committed Jan 28, 2024
1 parent 413de4f commit d39544d
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/6.deployment/1.database.md
Original file line number Diff line number Diff line change
@@ -7,13 +7,13 @@ description: "DipDup officially supports SQLite, PostgreSQL and TimescaleDB as a

DipDup officially supports SQLite, PostgreSQL and TimescaleDB as a database engine. This table will help you choose a database engine that mostly suits your needs.

| | SQLite | PostgreSQL | TimescaleDB |
|:-------------------- |:-----------------:|:-------------:|:-----------------------:|
| Recommended versions | latest | 14, 15 | 14, 15 |
| | SQLite | PostgreSQL | TimescaleDB |
|:-------------------- |:----------------- |:------------- |:----------------------- |
| Recommended versions | latest | 14, 15 | 14, 15 |
| Best application | early development | general usage | working with timeseries |
| SQL scripts | | | |
| Immune tables | | | |
| Hasura integration | | | |
| SQL scripts | 🟢 | 🟢 | 🟢 |
| Immune tables | ⚠️ | 🟢 | 🟢 |
| Hasura integration | 🔴 | 🟢 | 🟢 |

By default, DipDup uses an in-memory SQLite database that is destroyed after the process exits.

0 comments on commit d39544d

Please sign in to comment.