taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 39137d43da8a7cfce29aaecdb64b33ea08a07b10
parent 7d9da3af3edd78500a949740b2a558b448cb462c
Author: Christian Grothoff <grothoff@gnunet.org>
Date:   Wed, 30 Nov 2022 11:50:38 +0100

document DB design

Diffstat:
Mdesign-documents/033-database.rst | 10++++++++++
1 file changed, 10 insertions(+), 0 deletions(-)

diff --git 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 ============