summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Grothoff <grothoff@gnunet.org>2022-11-30 11:50:38 +0100
committerChristian Grothoff <grothoff@gnunet.org>2022-11-30 11:50:38 +0100
commit39137d43da8a7cfce29aaecdb64b33ea08a07b10 (patch)
tree476f2b145a4aa8a194221d84a08de8592e55ebad
parent7d9da3af3edd78500a949740b2a558b448cb462c (diff)
downloaddocs-39137d43da8a7cfce29aaecdb64b33ea08a07b10.tar.gz
docs-39137d43da8a7cfce29aaecdb64b33ea08a07b10.tar.bz2
docs-39137d43da8a7cfce29aaecdb64b33ea08a07b10.zip
document DB design
-rw-r--r--design-documents/033-database.rst10
1 files changed, 10 insertions, 0 deletions
diff --git a/design-documents/033-database.rst b/design-documents/033-database.rst
index 760365fc..ec91f6dc 100644
--- a/design-documents/033-database.rst
+++ b/design-documents/033-database.rst
@@ -108,6 +108,16 @@ re-attach shards. So this will require additional stored
procedures to support operations on shards.
+Merchant details
+^^^^^^^^^^^^^^^^
+
+The merchant does not (yet) need any type of master table, as we do not
+(yet) use any kind of sharding or partitioning. There are also no
+stored procedures being used by the backend. Hence, it is simply the
+"versioning.sql"-controlled table creation/alteration sequence
+(merchant-0001.sql, etc.) and the "drop.sql" to reset everything.
+
+
Alternatives
============