| Summary: | ASTERISK-26010: [patch]func_odbc: single database connection should be optional | ||||
| Reporter: | Alexei Gradinari (alexei gradinari) | Labels: | |||
| Date Opened: | 2016-05-10 14:29:37 | Date Closed: | 2016-09-23 14:10:56 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Functions/func_odbc | ||
| Versions: | 13.9.0 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | func_odbc was changed in Asterisk 13.9.0 to make func_odbc use a single
database connection per DSN because of reported bug with MySQL/MariaDB LAST_INSERT_ID(). This is drawback in performance when func_odbc is used very often in dialplan. Single database connection should be optional. Meanwhile... even with not persistent connection the stored routine (procedure or function) can be used to get correct LAST_INSERT_ID value. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-05-10 14:29:38.682-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. | ||||