mirror of
https://github.com/asterisk/asterisk.git
synced 2026-05-05 04:43:44 +00:00
095108273b
a backslash. Unfortunately, this does not universally work on all databases, since on databases which natively use the backslash as a delimiter, the backslash itself needs to be delimited, but on other databases that have no delimiter, backslashing the backslash causes an error. So the only solution that I can come up with is to create an option in res_odbc that explicitly specifies whether or not backslash is a native delimiter. If it is, we use it natively; if not, we use the ESCAPE clause to make it one. Reported by: elguero Patch by: tilghman (Closes issue #11364) git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@89559 65c4cc65-6c06-0410-ace0-fbb531ad65f3
45 lines
1.0 KiB
Plaintext
45 lines
1.0 KiB
Plaintext
;;; odbc setup file
|
|
|
|
; ENV is a global set of environmental variables that will get set.
|
|
; Note that all environmental variables can be seen by all connections,
|
|
; so you can't have different values for different connections.
|
|
[ENV]
|
|
INFORMIXSERVER => my_special_database
|
|
INFORMIXDIR => /opt/informix
|
|
|
|
; All other sections are arbitrary names for database connections.
|
|
|
|
[asterisk]
|
|
enabled => no
|
|
dsn => asterisk
|
|
;username => myuser
|
|
;password => mypass
|
|
pre-connect => yes
|
|
|
|
|
|
[mysql2]
|
|
enabled => no
|
|
dsn => MySQL-asterisk
|
|
username => myuser
|
|
password => mypass
|
|
pre-connect => yes
|
|
|
|
; Certain servers, such as MS SQL Server and Sybase use the TDS protocol, which
|
|
; limits the number of active queries per connection to 1. By setting up pools
|
|
; of connections, Asterisk can be made to work with these servers.
|
|
[sqlserver]
|
|
enabled => no
|
|
dsn => mickeysoft
|
|
pooling => yes
|
|
limit => 5
|
|
username => oscar
|
|
password => thegrouch
|
|
pre-connect => yes
|
|
; Many databases have a default of '\' to escape special characters. MS SQL
|
|
; Server does not.
|
|
backslash_is_escape => no
|
|
|
|
|
|
|
|
|