taler-docs

commit 368d64189b6354b645f3d289374a02fb497a57da
parent f864bd11633ec398373766df89eaad643ff6929e
Author: Stefan Kügel <stefan.kuegel@taler.net>
Date:   Wed, 22 Oct 2025 17:46:46 +0200

harmonise taler merchant db name, rectify typo in "taler-merchant", add safety note

Diffstat:
M
taler-merchant-manual.rst
 | 
7
+++++--

1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
@@ -553,17 +553,20 @@ DBMS-specific options to access the database.
    been created, so you can just run the tool without any arguments and should
    have a working database configuration.
 
+   Please make sure you did not create a taler merchant database manually before running
+   this command or it will fail with SQL errors.
+
 
 For the ``postgres`` backend, you need to specify:
 
 .. code-block:: ini
 
       [merchantdb-postgres]
-      CONFIG = "postgres:///talermerchant"
+      CONFIG = "postgres:///taler-merchant"
 
 This option specifies a PostgreSQL access path, typically using the format
 ``postgres:///$DBNAME``, where ``$DBNAME`` is the name of the PostgreSQL
-database you want to use (here, ``talermerchant`` on the local machine).
+database you want to use (here, ``taler-merchant`` on the local machine).
 Suppose ``$USER`` is the name of the user who will run the backend process
 (usually ``taler-merchant-httpd``). Then, you need to first run: