[asterisk-bugs] [JIRA] (ASTERISK-22272) [patch] Unexepected behaviour with adaptive odbc filter

[Jordi Llull Chavarría (JIRA)]

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

Jordi Llull Chavarría updated ASTERISK-22272:
---------------------------------------------

    Attachment: cdr_adaptive_odbc.diff
    
> [patch] Unexepected behaviour with adaptive odbc filter
> -------------------------------------------------------
>
>                 Key: ASTERISK-22272
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22272
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/cdr_adaptive_odbc
>    Affects Versions: 11.4.0
>            Reporter: Jordi Llull Chavarría
>            Severity: Minor
>         Attachments: cdr_adaptive_odbc.diff
>
>
> I was playing with our CDR configuration and I found an annoying behaviour when trying to replace the src column in some cases. My {{cdr_adaptive_odbc.conf}} contains something like this:
> [replace-src]
> connection=asterisk
> table=cdr
> alias source => src
> filter source != 
> [dont-replace-src]
> connection=asterisk
> table=cdr
> filter source =>
> So if you set CDR(source) in the dialplan it works great. However if you don't set it it'll make two rows for the CDR. That's because it won't check filters if the value is not set! The attached patch solves the problem by avoiding inserting the CDR if the column is not set and there's a non-blank filter for it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira