On Wednesday 22 April 2009 13:34:29 Kristina Harris wrote: > Hi, all. I've been searching google, bug reports and forums and have > looked in all the asterisk-users list archives back to 2003 but haven't > seen an answer to this, so thought I'd post here. > > The problem seems to be that Asterisk 1.6.0.5 is sending backslashes > (needed to escape commas and so forth in 1.4.21.2) as > *literal* backslashes to Mysql, so that Mysql gives a syntax error and > many things associated with app_addon_sql_mysql.c fail. I'm pretty sure > this is an asterisk thing and not an addon thing because the query has the > backslashes when app_addon_sql_mysql.c gets it whereas I would have > expected asterisk to have already used them to escape the commas, but I > could be wrong.
Correct. You no longer have to escape anything in the MYSQL command, at all. This was done as a one-time flag-day event, for the upgrade from 1.4 to 1.6. It makes future dialplans much easier to write, albeit with a one-time conversion. -- Tilghman _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
