From: Frank Louwers Date: Thu, 18 Apr 2019 14:04:50 +0000 (+0200) Subject: Point out that the sql schema is for 4.2/master in the guide. X-Git-Tag: rec-4.2.0-rc1~47^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0a4537718b3657dc29afbfac05279ef997dbbc3d;p=thirdparty%2Fpdns.git Point out that the sql schema is for 4.2/master in the guide. --- diff --git a/docs/guides/basic-database.rst b/docs/guides/basic-database.rst index 0a832e37c7..cffe9dbbbd 100644 --- a/docs/guides/basic-database.rst +++ b/docs/guides/basic-database.rst @@ -46,10 +46,24 @@ Example: configuring MySQL -------------------------- Connect to MySQL as a user with sufficient privileges and issue the -following commands: +following commands below if you are running the 4.2 or master version of PowerDNS: + +Please find `the 4.1 schema on GitHub `_. + .. literalinclude:: ../../modules/gmysqlbackend/schema.mysql.sql +We recommend you add the following MySQL statements as well. These will add +foreign key constraints to the tables in order to automate deletion of records, key +material, and other information upon deletion of a domain from the +domains table. These will only work on the InnoDB storage engine, but if you +followed our guide so far, that's exactly the engine we are using. + +The following SQL does the job: + +.. literalinclude:: ../../modules/gmysqlbackend/enable-foreign-keys.mysql.sql + + Now we have a database and an empty table. PowerDNS should now be able to launch in monitor mode and display no errors: