| Summary: | ASTERISK-24568: res_config_odbc fails on MS SQL Server | ||
| Reporter: | Rudolf Faix (rudolf.faix) | Labels: | |
| Date Opened: | 2014-11-29 23:31:09.000-0600 | Date Closed: | 2014-12-16 17:46:42.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_config_odbc |
| Versions: | 11.14.1 13.0.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | OpenSuse 13.1, FreeTDS, UnixODBC, MS SQL Server | Attachments: | |
| Description: | res_config_odbc fails on SQL-Server for the following statement:
ast_build_string(&sql, &sqlleft, "SELECT MAX(LENGTH(var_val)) FROM %s WHERE filename='%s'", table, file); If you exchange the word "LENGTH" to "LEN" everything is working fine: ast_build_string(&sql, &sqlleft, "SELECT MAX(LEN(var_val)) FROM %s WHERE filename='%s'", table, file); | ||
| Comments: | By: Matt Jordan (mjordan) 2014-12-02 13:32:56.186-0600 Microsoft SQL Server receives little to no interoperability support, given its relative infrequent use with Asterisk. While this is an interoperability issue, it is unlikely to get fixed without a patch. If you're not interested in providing a patch, this issue will most likely get closed a "Won't Fix". Note that changing this from {{LENGTH}} to {{LEN}} is not appropriate, as that would break compatibility with other database drivers. By: Rusty Newton (rnewton) 2014-12-16 17:46:42.302-0600 Yup - [New Feature Guidelines|https://wiki.asterisk.org/wiki/display/AST/New+Feature+Guidelines] Closing out until we have a patch. [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. | ||