From 47a01fa172b1a018ad36296cd00ad1ecb2f54897 Mon Sep 17 00:00:00 2001 From: Christian Hofstaedtler Date: Sat, 7 Feb 2015 14:32:17 +0100 Subject: [PATCH] docs: Remove remains of gsqlite(2) It has been removed in 2012. --- docs/markdown/authoritative/backend-gsqlite.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/markdown/authoritative/backend-gsqlite.md b/docs/markdown/authoritative/backend-gsqlite.md index d77754970..d2dd0fdf1 100644 --- a/docs/markdown/authoritative/backend-gsqlite.md +++ b/docs/markdown/authoritative/backend-gsqlite.md @@ -1,4 +1,4 @@ -# Generic SQLite backend (2 and 3) +# Generic SQLite backend | | | |:--|:--| |Native|Yes| @@ -17,12 +17,12 @@ This backend retrieves all data from a SQLite database, which is an RDBMS that's As this is a generic backend, built on top of the gSql framework, you can specify all queries as documented in [Generic MySQL and PostgreSQL backends](backend-generic-mypgsql.md#queries-and-settings). -SQLite exists in two incompatible versions, numbered 2 and 3, and from 2.9.21 onwards, PowerDNS supports both. It is recommended to go with version 3 as it is newer, has better performance and is actively maintained. To use version 3, choose `launch=gsqlite3`. +SQLite exists in two incompatible versions, PowerDNS only supports version 3. To launch the backend, put `launch=gsqlite3` in the configuration. ## Compiling the SQLite backend Before you can begin compiling PowerDNS with the SQLite backend you need to have the SQLite utility and library installed on your system. You can download these from , or you can use packages (if your distribution provides those). -When you've installed the library you can use: `./configure --with-modules="gsqlite"` or `./configure --with-modules="gsqlite3"` to configure PowerDNS to use the SQLite backend. Compilation can then proceed as usual. +When you've installed the library you can use: `./configure --with-modules="gsqlite3"` to configure PowerDNS to use the SQLite backend. Compilation can then proceed as usual. SQLite is included in most PowerDNS binary releases. @@ -35,9 +35,9 @@ Before you can use this backend you first have to set it up and fill it with dat This schema contains all elements needed for master, slave and superslave operation. -After you have created the database you probably want to fill it with data. If you have a BIND zone file it's as easy as: `zone2sql --zone=myzonefile --gsqlite | sqlite powerdns.sqlite`, but you can also use AXFR (or insert data manually). +After you have created the database you probably want to fill it with data. If you have a BIND zone file it's as easy as: `zone2sql --zone=myzonefile --gsqlite | sqlite3 powerdns.sqlite3`, but you can also use AXFR (or insert data manually). -To communicate with a SQLite database, use either the 'sqlite' or 'sqlite3' program, and feed it SQL. +To communicate with a SQLite database, use the `sqlite3` program, and feed it SQL. ## Configuration Parameters These are the configuration file parameters that are available for the gsqlite3 backend. @@ -59,8 +59,8 @@ The last thing you need to do is telling PowerDNS to use the SQLite backend. ``` # in pdns.conf -launch=gsqlite # or gsqlite3 -gsqlite-database= # or gsqlite3-database +launch=gsqlite3 +gsqlite3-database= ``` Then you can start PowerDNS and it should notify you that a connection to the database was made. -- 2.40.0