[Home]

Summary:ASTERISK-26001: cel, odbc: Asterisk ignores dateformat setting in cel.conf and default behaviour wrong
Reporter:Richard Wilkinson (rickead2000)Labels:
Date Opened:2016-05-06 13:05:42Date Closed:
Priority:MinorRegression?
Status:Open/NewComponents:CEL/cel_odbc CEL/General
Versions:13.8.2 13.9.0 Frequency of
Occurrence
Constant
Related
Issues:
is duplicated byASTERISK-29162 dateformat ignored for CEL ODBC connection
Environment:Centos LinuxAttachments:
Description: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.


Comments:By: Asterisk Team (asteriskteam) 2016-05-06 13:05:43.486-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

By: Rusty Newton (rnewton) 2016-05-09 09:20:52.056-0500

Do you see the same problem with CSV? Or only when using OBDC + MySQL?

By: Richard Wilkinson (rickead2000) 2016-05-10 08:50:45.763-0500

It works correct and as expected in CSV