[asterisk-bugs] [Asterisk 0013520]: MYSQL INSERT Query length

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Sep 19 08:30:29 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13520 
====================================================================== 
Reported By:                ariko
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13520
Category:                   Addons/app_addon_sql_mysql
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.21.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-19 08:15 CDT
Last Modified:              2008-09-19 08:30 CDT
====================================================================== 
Summary:                    MYSQL INSERT Query length
Description: 
I use extensions stored in mysql and from these extensions call mysql
queries using app_addon_sql_mysql. 
everything is ok at all but when I call query with larger number of
characters - greater that 495 chars- I got missing characters in the end
and my mysql query crash. 
Anyone notice this or fix this issue ? 

 
====================================================================== 

---------------------------------------------------------------------- 
 (0092698) blitzrage (administrator) - 2008-09-19 08:30
 http://bugs.digium.com/view.php?id=13520#c92698 
---------------------------------------------------------------------- 
This most likely has to do with the line length available in the Asterisk
dialplan. If you need to run queries longer than this, a better method is
really to use func_odbc to create a custom function in which you won't be
restricted by the dialplan.

I'm gonna leave this open for now in case anyone else wants to comment on
it, but I think this is just a line length restriction of the dialplan, and
not an issue with the MYSQL() application itself. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-19 08:30 blitzrage      Note Added: 0092698                          
======================================================================




More information about the asterisk-bugs mailing list