[asterisk-bugs] [JIRA] (ASTERISK-26001) cel, odbc: Asterisk ignores dateformat setting in cel.conf and default behaviour wrong
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Thu Jun 2 09:52:56 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-26001:
------------------------------------
Summary: cel, odbc: Asterisk ignores dateformat setting in cel.conf and default behaviour wrong (was: cel: Asterisk ignores dateformat setting in cel.conf and default behaviour wrong)
> cel, odbc: Asterisk ignores dateformat setting in cel.conf and default behaviour wrong
> --------------------------------------------------------------------------------------
>
> Key: ASTERISK-26001
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26001
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: CEL/cel_odbc, CEL/General
> Affects Versions: 13.8.2, 13.9.0
> Environment: Centos Linux
> Reporter: Richard Wilkinson
> Severity: Minor
>
> Asterisk ignores the dateformat configuration parameter in cel.conf when using ODBC with MySQL. This may be apparant with other DB backends but I don't have means to test those.
> Asterisk is pushing the date string to to the database incorrectly. I have ruled out MySQL reformatting the unix timestamp.
> Documentation states omitting the parameter defaults it to seconds.microseconds.
> Whatever the value is specified, the format actually used is yyyy-mm-dd hh:mm:ss.microseconds.
> Here are some examples:-
> Parameter: Omitted
> Date Generated: 2016-05-06 18:58:21.416305
> Parameter: dateformat = %s
> Date Generated: 2016-05-06 18:58:21.416305
> Parameter: dateformat = "%F %T"
> Date Generated: 2016-05-06 18:58:21.416305
> It is completely ignoring what dateformat is set to.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list