From 13204f9c20a03dcc041cd22fff22fb28af569eaf Mon Sep 17 00:00:00 2001
From: "Jeremy C. Reed" <jreed@ISC.org>
Date: Thu, 24 Feb 2011 07:51:18 -0600
Subject: [PATCH] [jreed-docs] in-memory datasource exists now

so sqlite3 is not the only one.

TODO: still need to document the in-memory datasource.
---
 doc/guide/bind10-guide.xml | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index 3670c460ad..20678543b1 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -79,9 +79,7 @@
       </para>
 
       <note><para>
-	For this development prototype release, the only supported
-	data source backend is SQLite3. The authoritative server
-	requires SQLite 3.3.9 or newer.
+	The authoritative server requires SQLite 3.3.9 or newer.
 	The <command>b10-xfrin</command>, <command>b10-xfrout</command>,
 	and <command>b10-zonemgr</command> modules require the
 	libpython3 library and the Python _sqlite3.so module.
@@ -1108,9 +1106,10 @@ This may be a temporary setting until then.
 
       <note><para>
         For the development prototype release, <command>b10-auth</command>
-        only supports the SQLite3 data source backend.
+        supports a SQLite3 data source backend and in-memory data source
+        backend.
         Upcoming versions will be able to use multiple different
-        data sources, such as MySQL, Berkeley DB, or in-memory DB.
+        data sources, such as MySQL and Berkeley DB.
       </para></note>