From 4d2c259aa2f39b8ee0d6d80ffab96688b372fef0 Mon Sep 17 00:00:00 2001 From: Ben Scott Date: Wed, 18 Jun 2025 14:39:14 -0400 Subject: [PATCH] [#3881] Adapt d85666cf to this rewrite --- doc/sphinx/arm/config-backend.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/sphinx/arm/config-backend.rst b/doc/sphinx/arm/config-backend.rst index 7e4871ebdd..23269d5ae9 100644 --- a/doc/sphinx/arm/config-backend.rst +++ b/doc/sphinx/arm/config-backend.rst @@ -219,11 +219,11 @@ Installation To use either Configuration Backend, the appropriate module library (:ischooklib:`libdhcp_mysql.so` or :ischooklib:`libdhcp_pgsql.so`) must be compiled during the Kea build. The ``-D`` switch specifies which database -module to build, if any: ``-D mysql`` or ``-D pgsql``. The appropriate -database client libraries and header files must be installed prior to build. -See :ref:`dhcp-install-configure` for more information on building Kea with -database support. ISC's Kea packaging, as well as some distributions, provide -separate packages for each database type. +module to build, if any: ``-D mysql=enabled`` or ``-D pgsql=enabled``. The +appropriate database client libraries and header files must be installed prior +to build. See :ref:`dhcp-install-configure` for more information on building +Kea with database support. ISC's Kea packaging, as well as some third-party +distributions, provide separate packages for each database type. The database server hosting the CB tables must be prepared with the Kea schema. When upgrading an existing Kea installation, the database schema may