From d0e2ac9ed2432e877e1a55f46752b614d29fafb9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micka=C3=ABl=20R=C3=A9mond?= Date: Sun, 3 Sep 2006 15:15:46 +0000 Subject: * src/odbc/odbc_queries.erl: Support for Microsoft SQL Server as a database backend (via ODBC). * src/odbc/ejabberd_odbc.erl: Likewise. * src/odbc/mssql.sql: Likewise. * src/odbc/Makefile.in: Likewise. * src/ejabberd_auth_odbc.erl: Likewise. * src/mod_offline_odbc.erl: Likewise. * src/mod_roster_odbc.erl: Likewise. * src/mod_last_odbc.erl: Likewise. * src/configure.ac: Likewise * doc/guide.tex: Likewise. * doc/introduction.tex: Likewise. * src/odbc/pg.sql: Minor fix. SVN Revision: 598 --- doc/guide.tex | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'doc/guide.tex') diff --git a/doc/guide.tex b/doc/guide.tex index 99e2df91a..0a757ca58 100644 --- a/doc/guide.tex +++ b/doc/guide.tex @@ -860,6 +860,26 @@ available from: \subsection{Relational Database Support} \label{sec:relationaldatabase} +\subsubsection{Preliminary steps} +\label{sec:relationaldatabasecompilation} + +If you have installed ejabberd using a binary version, the compilation steps +are not needed as they have already been done correctly. + +Otherwise, to be able to use ejabberd with a relational database you need to +enable ODBC modules during compilation, even if you want to use ejabberd with +MySQL or PostgreSQL in native mode. The following \term{configure} command can +be used to enable the relational modules: +\begin{verbatim} +./configure --enable-odbc +\end{verbatim} + +If you are planning to use Microsoft SQL Server with ODBC, you need to specify +it from the \term{configure} command before compilation: +\begin{verbatim} +./configure --enable-odbc --enable-mssql +\end{verbatim} + \subsubsection{Authentication against a relational database} \label{sec:relationaldatabaseauth} -- cgit v1.2.3