diff options
| author | Alexei Gradinari <alex2grad@gmail.com> | 2016-05-10 15:30:29 -0400 |
|---|---|---|
| committer | Alexei Gradinari <alex2grad@gmail.com> | 2016-05-20 13:25:45 -0400 |
| commit | cd89501d48b516ef03957bd39cdd8180b4684a56 (patch) | |
| tree | baac26a0860596cfa10f976bc2abe8e797475ae3 /configs | |
| parent | 2d4c818ac1303bb076ea5fbdd5587d138ae3e6cf (diff) | |
func_odbc: single database connection should be optional
func_odbc was changed in Asterisk 13.9.0
to make func_odbc use a single database connection per DSN
because of reported bug ASTERISK-25938
with MySQL/MariaDB LAST_INSERT_ID().
This is drawback in performance when func_odbc is used
very often in dialplan.
Single database connection should be optional.
ASTERISK-26010
Change-Id: I57d990616c957dabf7597dea5d5c3148f459dfb6
Diffstat (limited to 'configs')
| -rw-r--r-- | configs/samples/func_odbc.conf.sample | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/configs/samples/func_odbc.conf.sample b/configs/samples/func_odbc.conf.sample index fd528d216..8614bf12a 100644 --- a/configs/samples/func_odbc.conf.sample +++ b/configs/samples/func_odbc.conf.sample @@ -1,6 +1,20 @@ ; ; func_odbc.conf ; +[general] +; +; Asterisk uses separate connections for every database operation. +; If single_db_connection is enabled then func_odbc will use a single +; database connection per DSN. +; This option exists for those who expect that a second func_odbc call +; works on the same connection. That allows you to do a LAST_INSERT_ID() +; in a second func_odbc call. +; Note that you'll need additional dialplan locks for this behaviour to work. +; There are better ways: using stored procedures/functions instead. +; This option is enabled by default. +;single_db_connection=yes +; +; ; Each context is a separately defined function. By convention, all ; functions are entirely uppercase, so the defined contexts should also ; be all-uppercase, but there is nothing that enforces this. All functions |