diff options
author | Erik Johnston <erik@matrix.org> | 2019-12-04 14:00:29 +0000 |
---|---|---|
committer | Erik Johnston <erik@matrix.org> | 2019-12-05 10:46:37 +0000 |
commit | 8863624f7852ffc4a261aa9d17f6f7ddb5bf0c19 (patch) | |
tree | 964dcbc48f8af62a735880eb03b57bf4dee6c9ca /synapse/storage/__init__.py | |
parent | Move DB pool and helper functions into dedicated Database class (diff) | |
download | synapse-8863624f7852ffc4a261aa9d17f6f7ddb5bf0c19.tar.xz |
Comments
Diffstat (limited to 'synapse/storage/__init__.py')
-rw-r--r-- | synapse/storage/__init__.py | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/synapse/storage/__init__.py b/synapse/storage/__init__.py index 0460fe8cc9..8fb18203dc 100644 --- a/synapse/storage/__init__.py +++ b/synapse/storage/__init__.py @@ -17,10 +17,10 @@ """ The storage layer is split up into multiple parts to allow Synapse to run against different configurations of databases (e.g. single or multiple -databases). The `data_stores` are classes that talk directly to a single -database and have associated schemas, background updates, etc. On top of those -there are (or will be) classes that provide high level interfaces that combine -calls to multiple `data_stores`. +databases). The `Database` class represents a single physical database. The +`data_stores` are classes that talk directly to a `Database` instance and have +associated schemas, background updates, etc. On top of those there are classes +that provide high level interfaces that combine calls to multiple `data_stores`. There are also schemas that get applied to every database, regardless of the data stores associated with them (e.g. the schema version tables), which are |