From 4b5ef8f2cefbddfaa468fe30a0a205da51b330d2 Mon Sep 17 00:00:00 2001
From: Badlop <badlop@process-one.net>
Date: Sat, 21 Aug 2010 18:56:01 +0200
Subject: [PATCH] Add mod_pubsub_odbc to list of ODBC modules (EJAB-1293)

---
 doc/guide.html | 5 +++--
 doc/guide.tex  | 5 +++--
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/doc/guide.html b/doc/guide.html
index 57873a873..50cdca74a 100644
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -1944,8 +1944,8 @@ Mnesia as backend.
 (see&#XA0;<A HREF="#database">3.2</A>) as backend.
 </LI><LI CLASS="li-itemize">&#X2018;_ldap&#X2019;, this means that the module needs an LDAP server as backend.
 </LI></UL><P>If you want to,
-it is possible to use a relational database to store pieces of
-information. You can do this by changing the module name to a name with an
+it is possible to use a relational database to store the tables created by some ejabberd modules.
+You can do this by changing the module name to a name with an
 <TT>_odbc</TT> suffix in <TT>ejabberd</TT> config file. You can use a relational
 database for the following data:</P><UL CLASS="itemize"><LI CLASS="li-itemize">
 Last connection date and time: Use <TT>mod_last_odbc</TT> instead of
@@ -1956,6 +1956,7 @@ Last connection date and time: Use <TT>mod_last_odbc</TT> instead of
 </LI><LI CLASS="li-itemize">Users&#X2019; VCARD: Use <TT>mod_vcard_odbc</TT> instead of <TT>mod_vcard</TT>.
 </LI><LI CLASS="li-itemize">Private XML storage: Use <TT>mod_private_odbc</TT> instead of <TT>mod_private</TT>.
 </LI><LI CLASS="li-itemize">User rules for blocking communications: Use <TT>mod_privacy_odbc</TT> instead of <TT>mod_privacy</TT>.
+</LI><LI CLASS="li-itemize">Pub-Sub nodes, items and subscriptions: Use <TT>mod_pubsub_odbc</TT> instead of <TT>mod_pubsub</TT>.
 </LI></UL><P>You can find more
 <A HREF="http://www.ejabberd.im/contributions">contributed modules</A> on the
 <TT>ejabberd</TT> website. Please remember that these contributions might not work or
diff --git a/doc/guide.tex b/doc/guide.tex
index 044fab829..73f848f52 100644
--- a/doc/guide.tex
+++ b/doc/guide.tex
@@ -2560,8 +2560,8 @@ You can see which database backend each module needs by looking at the suffix:
 \end{itemize}
 
 If you want to,
-it is possible to use a relational database to store pieces of
-information. You can do this by changing the module name to a name with an
+it is possible to use a relational database to store the tables created by some ejabberd modules.
+You can do this by changing the module name to a name with an
 \term{\_odbc} suffix in \ejabberd{} config file. You can use a relational
 database for the following data:
 
@@ -2574,6 +2574,7 @@ database for the following data:
 \item Users' VCARD: Use \term{mod\_vcard\_odbc} instead of \term{mod\_vcard}.
 \item Private XML storage: Use \term{mod\_private\_odbc} instead of \term{mod\_private}.
 \item User rules for blocking communications: Use \term{mod\_privacy\_odbc} instead of \term{mod\_privacy}.
+\item Pub-Sub nodes, items and subscriptions: Use \term{mod\_pubsub\_odbc} instead of \term{mod\_pubsub}.
 \end{itemize}
 
 You can find more