[asterisk-bugs] [JIRA] (ASTERISK-26010) [patch]func_odbc: single database connection should be optional

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230539#comment-230539 ] 

Asterisk Team commented on ASTERISK-26010:
------------------------------------------

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].

> [patch]func_odbc: single database connection should be optional
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-26010
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26010
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Functions/func_odbc
>    Affects Versions: 13.9.0
>            Reporter: Alexei Gradinari
>
> 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) should be used to get correct LAST_INSERT_ID value.



--
This message was sent by Atlassian JIRA
(v6.2#6252)