[asterisk-bugs] [JIRA] (ASTERISK-20504) Asterisk 1.8 should use [compat] section in asterisk.conf and behave acconding to the flag pbx_realtime=1.6

[Rusty Newton (JIRA)]

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

Rusty Newton closed ASTERISK-20504.
-----------------------------------

    Resolution: Not A Bug

This is being close as a feature request or improvement, with no patch. If someone provides a patch for the requested functionality for queue_log backwards compatibility then the issue can be re-opened.

https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines
                
> Asterisk 1.8 should use [compat] section in asterisk.conf and behave acconding to the flag pbx_realtime=1.6
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20504
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20504
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Addons/res_config_mysql, Applications/app_queue
>    Affects Versions: 1.8.16.0
>         Environment: Debian wheezy, mysql (using addon res_config_mysql)
>            Reporter: Tiago Geada
>            Assignee: Matt Jordan
>
> in 1.6 queue_log was being populated with the column 'time' formated as UNIX TIME STAMP, while in 1.8, res_config starts by complaining about column time being varchar(11) while it should be char(26) and every queue event is registered with datetime format (as in '2012-10-02 00:01:04') instead of '1349132464'
> I thought in asterisk.conf [compat] section having "pbx_realtime=1.6" would take care of this, but it does not.
> Shouldn't date be inserted as unixtimestamp, if this compat flag is set to 1.6 ??
> Also, maintaining this compatibility, queue_log should still need only one 'data' column, instead of 'data1','data2','data3','data4' and 'data5'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira