[asterisk-bugs] [Asterisk 0017077]: [patch] Fix query with double backslash in string literals and stop log warnings

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17077 
====================================================================== 
Reported By:                korihor
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17077
Category:                   Resources/res_config_pgsql
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.2.6 
JIRA:                       SWP-1132 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-03-22 21:49 CDT
Last Modified:              2011-04-18 12:00 CDT
====================================================================== 
Summary:                    [patch] Fix query with double backslash in string
literals and stop log warnings
Description: 
The function realtime_multi_pgsql use "LIKE '\\_%'" when look for a pattern
on realtime dialplan, that is a no standard use for "\\" in literal
strings.

This causes the postgresql logfile to be filled with a lot of warnings.

The correct is use "LIKE E'\\_%'".

This patch too set a more consistent level of verbosity for a log entry.
====================================================================== 

---------------------------------------------------------------------- 
 (0133883) rgagnon (reporter) - 2011-04-18 12:00
 https://issues.asterisk.org/view.php?id=17077#c133883 
---------------------------------------------------------------------- 
This might now mean a new configuration value would have to be put into
asterisk so users can indicate the version of postgresql in use, so that
asterisk can then know if it is to use the old, or new format.

I would imagine that having the leading "E" in the strings under older
pgsql implementations would break for them. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-18 12:00 rgagnon        Note Added: 0133883                          
======================================================================