From 6ab028735f2a5a98cbfe1fe2bf1e2d553405789a Mon Sep 17 00:00:00 2001 From: tilghman Date: Sun, 25 Nov 2007 17:50:07 +0000 Subject: Merged revisions 89559 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r89559 | tilghman | 2007-11-25 11:17:10 -0600 (Sun, 25 Nov 2007) | 14 lines 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/trunk@89561 f38db490-d61c-443f-a65b-d21fe96a405b --- configs/res_odbc.conf.sample | 3 +++ 1 file changed, 3 insertions(+) (limited to 'configs/res_odbc.conf.sample') diff --git a/configs/res_odbc.conf.sample b/configs/res_odbc.conf.sample index 617555fef..2fd9aa702 100644 --- a/configs/res_odbc.conf.sample +++ b/configs/res_odbc.conf.sample @@ -40,6 +40,9 @@ username => oscar password => thegrouch pre-connect => yes sanitysql => select count(*) from systables +; Many databases have a default of '\' to escape special characters. MS SQL +; Server does not. +backslash_is_escape => no -- cgit v1.2.3