From 88a1afbba392fb55455abcfedfeea103102b0d54 Mon Sep 17 00:00:00 2001
From: Stefan Ritt <stefan.ritt@psi.ch>
Date: Thu, 3 Jul 2003 12:52:02 +0000
Subject: [PATCH] *** empty log message ***

SVN revision: 569
---
 doc/config.html |  2 +-
 doc/faq.html    | 11 ++++++++++-
 2 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/doc/config.html b/doc/config.html
index 2123c9e0..1763a243 100755
--- a/doc/config.html
+++ b/doc/config.html
@@ -580,7 +580,7 @@ Number of logbook entries displayed per page in a search result. The default is
 <UL>
 <LI><b><code>Attributes = &lt;list&gt;</code></b>
 <br>
-Define a number of attributes for the logbook. A maximum of 20 attributes can be
+Define a number of attributes for the logbook. A maximum of 50 attributes can be
 defined. Typical values are "<I>Author</I>", "<I>Subject</I>" or "<I>Type</I>".
 <p>
 
diff --git a/doc/faq.html b/doc/faq.html
index a05adc3a..b48aa5b7 100755
--- a/doc/faq.html
+++ b/doc/faq.html
@@ -59,7 +59,16 @@ all logbooks, the above statements can be placed in the <b><code>[global]</code>
 
 <LI><a name=#2><b>Are there any plans to implement a MySQL back end?</b>
 <p>
-No. The idea behind <b>ELOG</b> is that it is a <I>simple to use, simple to install</I> application. Many people use <b>ELOG</b> under Windows, and they even don't know what MySQL means. Other people like the flat file database format, because it's simple, easily accessible from other programs, and it's easy to backup certain days or months of the database (since the filenames contain the date). Since <b>ELOG</b> should be independent of any other package, some "switchable" backend between native <b>ELOG</b> format and MySQL would be needed, which is lots of work and not planned right now.
+No. The idea behind <b>ELOG</b> is that it is a <I>simple to use, simple to install</I> application.
+Many people use <b>ELOG</b> under Windows, and they even don't know what MySQL means. Other people like
+the flat file database format, because it's simple, easily accessible from other programs, and it's easy
+to backup certain days or months of the database (since the filenames contain the date). Since <b>ELOG
+</b> should be independent of any other package, some "switchable" backend between native <b>ELOG</b>
+format and MySQL would be needed, which is lots of work and not planned right now.<p>
+
+However, there are several contributions from other people who wrote scripts to put ELOG entries
+into a MySQL database. One is available at
+<a href="http://midas.psi.ch/elogdemo/Forum/387">http://midas.psi.ch/elogdemo/Forum/387</a>.
 <p>
 
 <LI><a name=#3><b>Can I run the ELOG daemon from inside Apache or any other Web server?</b>