[asterisk-bugs] [JIRA] (ASTERISK-25955) Make single-connection per dns for func_odbc optional

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp closed ASTERISK-25955.
----------------------------------

    Resolution: Suspended

Someone else has submitted a fix for this on ASTERISK-26010 so tracking it there instead.

> Make single-connection per dns for func_odbc optional
> -----------------------------------------------------
>
>                 Key: ASTERISK-25955
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25955
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Functions/func_odbc
>    Affects Versions: 13.8.2
>            Reporter: Walter Doekes
>            Assignee: Walter Doekes
>
> Change Iac961fe79154c6211569afcdfec843c0c24c46dc (https://github.com/asterisk/asterisk/commit/7f8d83fef42f4b1d2240ea543f61a5a70754e862 ) fixes ASTERISK-25938 where a dialplan user was expecting a single connection for his func_odbc calls.
> The changeset fixes that a single ODBC connection is used for all func_odbc calls. I.e. no concurrent requests.
> In the report, the reporter was doing something like this:
> {noformat}
> Set(ODBC_do_some_write()=x)
> Set(insert_id=${ODBC_get_last_insert_id()})
> {noformat}
> The above only makes sense if you surround that with an exclusive lock; which the user did.
> Using a lock like that is not the common case. So I'd like the aforementioned fix to be optional -- possibly even disabled by default in master. That would give new users the benefits of concurrent access, while leaving asterisk-13 users (and those who explicitly choose to) with a single connection so the esoteric dialplan above works.
> ----
> Yes, this is an RFE without patch. I'll get to that, but first when we start moving some machines to 13.



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