From e805dec1415020113d1a9cd2e5555b946bb9956d Mon Sep 17 00:00:00 2001 From: Daniel Vaz Gaspar Date: Wed, 26 Apr 2023 14:28:42 +0100 Subject: [PATCH] docs: discourage the use of SQLite (#23794) --- docs/docs/installation/configuring-superset.mdx | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/docs/installation/configuring-superset.mdx b/docs/docs/installation/configuring-superset.mdx index 7f80cc1b7..9be7b8e85 100644 --- a/docs/docs/installation/configuring-superset.mdx +++ b/docs/docs/installation/configuring-superset.mdx @@ -71,9 +71,11 @@ WTF_CSRF_EXEMPT_LIST = [‘’] ### Using a production metastore -By default Superset is configured to use SQLite, it's a simple and fast way to get you started -(no installation needed). But for production environments you should use a different database engine on -a separate host or container. +By default, Superset is configured to use SQLite, which is a simple and fast way to get started +(without requiring any installation). However, for production environments, +using SQLite is highly discouraged due to security, scalability, and data integrity reasons. +It's important to use only the supported database engines and consider using a different +database engine on a separate host or container. Superset supports the following database engines/versions: @@ -89,7 +91,6 @@ Use the following database drivers and connection strings: | ----------------------------------------- | --------------------------------- | ------------------------------------------------------------------------ | | [PostgreSQL](https://www.postgresql.org/) | `pip install psycopg2` | `postgresql://:@/` | | [MySQL](https://www.mysql.com/) | `pip install mysqlclient` | `mysql://:@/` | -| SQLite | No additional library needed | `sqlite://` | To configure Superset metastore set `SQLALCHEMY_DATABASE_URI` config key on `superset_config` to the appropriate connection string.