ELOG/elog
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

*** empty log message ***

Browse Source 
SVN revision: 569
This commit is contained in:
ritt
2003-07-03 12:52:02 +00:00
parent 61dd3ed373
commit 88a1afbba3
2 changed files with 11 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/config.html
+1 -1
View File
@@ -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>
doc/faq.html
+10 -1
View File
@@ -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>