You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "dpgaspar (via GitHub)" <gi...@apache.org> on 2023/04/26 13:28:50 UTC

[GitHub] [superset] dpgaspar commented on a diff in pull request #23794: docs: discourage the use of SQLite

dpgaspar commented on code in PR #23794:
URL: https://github.com/apache/superset/pull/23794#discussion_r1177882333


##########
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.

Review Comment:
   shorter but seems a bit confusing to say "another supported database engine on a separate host"



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org