[svn-commits] mvanbaak: trunk r106186 - /trunk/doc/tex/realtime.tex

[SVN commits to the Digium repositories]

Author: mvanbaak
Date: Wed Mar  5 15:19:06 2008
New Revision: 106186

URL: http://svn.digium.com/view/asterisk?view=rev&rev=106186
Log:
document var_metric usage to prevent bugreports that are actually configuration issues

(closes issue #12151)
Reported by: caio1982
Patches:
      DB_metric3.diff uploaded by caio1982 (license 22)

Modified:
    trunk/doc/tex/realtime.tex

Modified: trunk/doc/tex/realtime.tex
URL: http://svn.digium.com/view/asterisk/trunk/doc/tex/realtime.tex?view=diff&rev=106186&r1=106185&r2=106186
==============================================================================
--- trunk/doc/tex/realtime.tex (original)
+++ trunk/doc/tex/realtime.tex Wed Mar  5 15:19:06 2008
@@ -38,6 +38,20 @@
 modules that read configurations, there's no difference between a static
 file in the file system, like extensions.conf, and a configuration loaded
 from a database.
+
+You just have to always make sure the var\_metric values are properly set and
+ordered as you expect in your database server if you're using the static mode
+with ARA (either sequentially or with the same var\_metric value for everybody).
+
+If you have an option that depends on another one in a given configuration
+file (i.e, 'musiconhold' depending on 'agent' from agents.conf) but their
+var\_metric are not sequential you'll probably get default values being assigned for
+those options instead of the desired ones. You can still use the same
+var\_metric for all entries in your DB, just make sure the entries
+are recorded in an order that does not break the option dependency.
+
+That doesn't happen when you use a static file in the file system. Although
+this might be interpreted as a bug or limitation, it is not.
 
 \subsubsection{Realtime SIP friends}