;
; func_odbc.conf
;
; 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
; are case-sensitive, however.
;
; For substitution, you have ${ARG1}, ${ARG2} ... ${ARGn}
; for the arguments to each SQL statement.
;
; In addition, for write statements, you have ${VAL1}, ${VAL2} ... ${VALn}
; parsed, just like arguments, for the values.  In addition, if you want the
; whole value, never mind the parsing, you can get that with ${VALUE}.
;
;
; If you have data which may potentially contain single ticks, you may wish
; to use the dialplan function SQL_ESC() to escape the data prior to its
; inclusion in the SQL statement.

[FEATURES]
dsn=asterisk
read=SELECT value FROM user_features WHERE user_id = '${SQL_ESC(${ARG1})}' AND feature_id = '${SQL_ESC(${ARG2})}'

[DEVICES]
dsn=asterisk
read=SELECT device_tech, device_name FROM voip_devices WHERE user_name = '${SQL_ESC(${ARG1})}'

; ODBC_SQL - Allow an SQL statement to be built entirely in the dialplan
[SQL]
dsn=asterisk
read=${ARG1}
setvars=yes
colprefix=FIELD_

;escapecommas=no	; Normally, commas within a field are escaped such that each
			; field may be separated into individual variables with ARRAY.
			; This option turns that behavior off [default=yes].

