Changeset 2777 for pykota/trunk

Timestamp:

03/02/06 17:56:30 (19 years ago)

Author:

jerome

Message:

Use moge generic terms instead of "PostgreSQL".

Files:

• pykota/trunk/conf/pykota.conf.sample (modified) (4 diffs)

pykota/trunk/conf/pykota.conf.sample

@@ -182 +182 @@
 # Should the database caching mechanism be enabled or not ?
 # If unset, caching is disabled. Possible values Y/N/YES/NO
-# caching mechanism works with both PostgreSQL and OpenLDAP backends
+# caching mechanism works with both relationnal and OpenLDAP backends
 # but may be really interesting only with OpenLDAP.
 #
@@ -189 +189 @@
 # YOU MAY FIND IT INTERESTING ANYWAY, ESPECIALLY FOR LDAP.
 #
+# THERE'S NO GUARANTEE THAT THIS CACHING MECHANISM WILL IMPROVE
+# PERFORMANCE WITH RELATIONNAL BACKENDS. IT MIGHT EVEN MAKE
+# PERFORMANCE DECREASE. AS ALWAYS : YMMV.
+#
 # FYI, I ALWAYS SET IT TO YES !
 #
@@ -195 +199 @@
 # Should full job history be disabled ?
 # If unset or set to No, full job history is kept in the database.
-# This will be useful in the future when the report generator
-# will be written.
 # Disabling the job history can be useful with heavily loaded
 # LDAP servers, to not make the LDAP tree grow out of control.
-# Disabling the job history with the PostgreSQL backend works too
+# Disabling the job history with a relationnal backend works too
 # but it's probably less useful than with LDAP.
 disablehistory: No
-
 
 # Where to log ?
@@ -259 +260 @@
 # If the value is not set, and the mail attribute for the user
 # is not set in the PyKota storage, be it LDAP (see usermail directive
-# above) or PostgreSQL, then email messages are sent to 
+# above) or a relationnal one, then email messages are sent to 
 # username@smtpserver
 #