diff options
| author | tilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-11-25 17:17:10 +0000 |
|---|---|---|
| committer | tilghman <tilghman@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-11-25 17:17:10 +0000 |
| commit | e2576b4a0635ab0499ff83205f8c13540076e11e (patch) | |
| tree | ad8210c1c145247568c15b362c15e07a790acff9 /configs | |
| parent | f78841fc40fd954f2ce3a6fdcbe75ba2aa227efe (diff) | |
We previously attempted to use the ESCAPE clause to set the escape delimiter to
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: http://svn.digium.com/svn/asterisk/branches/1.4@89559 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs')
| -rw-r--r-- | configs/res_odbc.conf.sample | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/configs/res_odbc.conf.sample b/configs/res_odbc.conf.sample index 16a1e6b05..1cca8b0e7 100644 --- a/configs/res_odbc.conf.sample +++ b/configs/res_odbc.conf.sample @@ -35,6 +35,9 @@ 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 |