Tilghman Lesher f1de129e5f
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: https://origsvn.digium.com/svn/asterisk/trunk@89561 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2007-11-25 17:50:07 +00:00
2005-11-29 18:24:39 +00:00
2005-11-29 18:24:39 +00:00
2007-11-23 02:37:38 +00:00
2005-11-29 18:24:39 +00:00
2006-09-11 16:41:49 +00:00
2006-02-20 18:30:49 +00:00
2005-11-29 18:24:39 +00:00
2007-11-08 18:48:15 +00:00
2007-04-05 22:40:42 +00:00
2007-06-19 20:38:21 +00:00
2005-11-29 18:24:39 +00:00
2005-11-29 18:24:39 +00:00
2007-11-09 16:32:01 +00:00
2006-03-08 22:12:20 +00:00
2007-08-21 15:04:37 +00:00
2005-11-29 18:24:39 +00:00
2005-11-29 18:24:39 +00:00
2007-10-15 23:20:40 +00:00
2007-08-30 15:34:18 +00:00
2007-03-13 21:22:33 +00:00
2007-04-18 07:57:18 +00:00
2007-11-07 04:11:32 +00:00
closes issue #11363 ; where the pattern _20x. buried in an included context, didn't match 2012; There were a small set of problems to fix: 1. I needed NOT to score patterns unless you are at the end of the data string. 2. Capital N,X,Z and small n,x,z are OK in patterns. I canonicalize the patterns in the trie to caps. 3. When a pattern ends with dot or exclamation, CANMATCH/MATCHMORE should always report this pattern, no matter the length. With this commit, I also supplied the wish of Luigi, where the user can select which pattern matching algorithm to use, the old (legacy) pattern matcher, or the new, trie based matcher. The OLD matcher is the default. A new [general] section variable, extenpatternmatchnew, is added to the extensions.conf, and the example config has it set to false. If true, the new matcher is used. In all other respects, the context/exten structs are the same; the tries and hashtabs are formed, but in the new mode the tries are not used. A new CLI command 'dialplan set extenpatternmatch true/false' is provided to allow switching at run time. I beg users that are forced to return to the old matcher to please report the reason in the bug tracker. Measured the speed benefit of the new matcher against an impossibly large context with 10,000 extensions: the new matcher is 374 times faster.
2007-11-24 21:00:26 +00:00
2007-11-02 15:36:34 +00:00
2007-10-15 16:41:56 +00:00
2005-11-29 18:24:39 +00:00
2007-09-04 19:56:46 +00:00
2007-05-31 15:05:56 +00:00
2006-09-18 16:36:14 +00:00
2007-04-30 16:16:26 +00:00
2007-09-17 21:44:38 +00:00
2007-04-30 16:16:26 +00:00
2007-04-30 16:16:26 +00:00
2007-08-28 15:42:08 +00:00
2007-10-07 16:28:25 +00:00
2006-05-22 21:12:30 +00:00
2007-08-28 20:03:48 +00:00
2007-06-21 23:07:20 +00:00
2007-10-17 20:42:20 +00:00
2007-04-30 16:16:26 +00:00
2007-04-18 07:57:18 +00:00
2007-11-12 13:36:45 +00:00
2006-08-25 14:14:27 +00:00
2007-10-01 14:43:56 +00:00
2006-10-04 17:10:53 +00:00
2007-01-16 01:20:06 +00:00
2006-09-11 16:41:49 +00:00
2007-01-16 17:23:31 +00:00
2005-11-29 18:24:39 +00:00
2007-11-06 22:36:55 +00:00
2007-09-13 15:26:40 +00:00
2007-11-25 17:50:07 +00:00
2007-05-07 22:32:50 +00:00
2006-02-26 20:46:11 +00:00
2005-12-20 23:53:26 +00:00
2006-06-05 08:39:42 +00:00
2007-07-20 22:25:41 +00:00
2007-03-19 15:43:15 +00:00
2007-11-25 11:46:17 +00:00
2007-09-14 19:49:05 +00:00
2007-03-16 01:43:41 +00:00
2006-09-11 16:41:49 +00:00
2005-11-29 18:24:39 +00:00
2006-01-16 18:05:19 +00:00
2007-11-06 14:11:34 +00:00
2007-11-09 18:57:21 +00:00
2007-02-12 15:48:28 +00:00
2007-09-18 21:07:08 +00:00
2006-09-11 16:41:49 +00:00
2007-11-07 02:14:40 +00:00
f1de129e5f