[asterisk-bugs] [JIRA] (ASTERISK-24364) PJSIP realtime configuration via res_odbc with Oracle backend - Binding variable to :0 is not allowed in oracle

[Rusty Newton (JIRA)]

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

Rusty Newton updated ASTERISK-24364:
------------------------------------

    Summary: PJSIP realtime configuration via res_odbc with Oracle backend - Binding variable to :0 is not allowed in oracle  (was: PJSIP realtime configuration via res_odbc with Oracle backend)

> PJSIP realtime configuration via res_odbc with Oracle backend - Binding variable to :0 is not allowed in oracle
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24364
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24364
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip, Resources/res_odbc, Resources/res_pjsip
>    Affects Versions: 12.6.0
>            Reporter: HZMI8gkCvPpom0tM
>            Assignee: HZMI8gkCvPpom0tM
>         Attachments: asterisk_ora.png, bug.txt, odbc.log, registration_attempt_log.txt, related_configs_extraction.txt
>
>
> In case of using pjsip with oracle realtime over odbc.
> Asterisk try to execute queryes like 
> {{SELECT ID FROM ps_endpoints WHERE id =:0;}}
> Binding variable to :0 is not allowed in oracle (at least for version 10.2.0.5.x) 
> Query constantly return ORA-01403: no data found
> After it realtime registrations functionality of pjsip completely stop to work.
> PS: If to use binding variable names like 
> {{SELECT ID FROM ps_endpoints WHERE id =:var0;}}
> oracle works ok. 
> It is possible bug in oracle of course, but i think that change of naming notation for odbc binding variables can solve a lot of compatibility issues with different databases.



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