summaryrefslogtreecommitdiff
path: root/configs/res_config_mysql.conf.sample
diff options
context:
space:
mode:
authorRussell Bryant <russell@russellbryant.com>2009-06-30 17:15:09 +0000
committerRussell Bryant <russell@russellbryant.com>2009-06-30 17:15:09 +0000
commitd806ae0da0811f26d23fd241ede8840d09cf74e4 (patch)
treedfebbc536874af10244b599cdee0a956375d95af /configs/res_config_mysql.conf.sample
parent37358765668bdfd77e5b99a28e39f4f3a61362a8 (diff)
Rename res_mysql.conf to res_config_mysql.conf, make module support both
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@204422 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'configs/res_config_mysql.conf.sample')
-rw-r--r--configs/res_config_mysql.conf.sample40
1 files changed, 40 insertions, 0 deletions
diff --git a/configs/res_config_mysql.conf.sample b/configs/res_config_mysql.conf.sample
new file mode 100644
index 000000000..dfbbf49a8
--- /dev/null
+++ b/configs/res_config_mysql.conf.sample
@@ -0,0 +1,40 @@
+;
+; Sample configuration for res_config_mysql.c
+;
+; The value of dbhost may be either a hostname or an IP address.
+; If dbhost is commented out or the string "localhost", a connection
+; to the local host is assumed and dbsock is used instead of TCP/IP
+; to connect to the server.
+;
+; Multiple database contexts may be configured, with the caveat that
+; all context names should be unique and must not contain the slash ('/')
+; character. If you wish to separate reads from writes in your database
+; configuration, you specify the database (NOT HERE, in other files)
+; separated by a slash, read database first. If your database
+; specification does not contain a slash, the implication is that reads
+; and writes should be performed to the same database.
+;
+; For example, in extconfig.conf, you could specify a line like:
+; sippeers => mysql,readhost.asterisk/writehost.asterisk,sipfriends
+; and then define the contexts [readhost.asterisk] and [writehost.asterisk]
+; below.
+;
+; The requirements parameter is available only in Asterisk 1.6.1 and
+; later and must be present in all contexts. It specifies the behavior
+; when a column name is required by the system. The default behavior is
+; "warn" and simply sends a warning to the logger that the column does
+; not exist (or is of the wrong type or precision). The other two
+; possibilities are "createclose", which adds the column with the right
+; type and length, and "createchar", which adds the column as a char
+; type, with the appropriate length to accept the data. Note that with
+; the MySQL driver, both "createclose" and "createchar" will, on occasion,
+; widen a table column width to meet the requirements specified.
+;
+[general]
+;dbhost = 127.0.0.1
+;dbname = asterisk
+;dbuser = myuser
+;dbpass = mypass
+;dbport = 3306
+;dbsock = /tmp/mysql.sock
+;requirements=warn ; or createclose or createchar