| Summary: | ASTERISK-08919: AEL parses MYSQL wrong | ||
| Reporter: | tgledhill (tgledhill) | Labels: | |
| Date Opened: | 2007-03-01 16:21:54.000-0600 | Date Closed: | 2007-03-23 09:04:46 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | PBX/pbx_ael |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | AEL CODE: MYSQL(Query resultid ${connid} SELECT var1, var2 FROM did); PARSED INTO: MYSQL("Zap/1-1", "Query resultid 19 SELECT var1| var2 FROM did") AEL CODE: MYSQL(Query resultid ${connid} SELECT var1\, var2 FROM did); PARSED INTO: MYSQL("Zap/1-1", "Query resultid 19 SELECT var1\, var2 FROM did") Extensions.conf CODE: MYSQL(Query resultid ${connid} SELECT var1\, var2 FROM did) PARSED INTO: MYSQL("Zap/1-1", "Query resultid 18 SELECT var1, var2 FROM did") | ||
| Comments: | By: Steve Murphy (murf) 2007-03-01 16:37:09.000-0600 OK, I'll investigate this. By: Steve Murphy (murf) 2007-03-02 01:04:49.000-0600 Fixes committed to 1.4 in 57426; committed to trunk in 57438; The 1.2 backport in team/murf/AEL2-1.2 was updated via 57457. I've corrected behavior; escaped commas in AEL in app data, are replaced with just a comma before they are passed into the extension engine. The backslash is reintroduced for extensions.conf output. This behavior should match what pbx_config does with commas before passing them into the extension engine. I tested it against test cases similar to the one supplied. Many thanks for this lesson on ael/extensions.conf compatibility! | ||