[Home]

Summary:ASTERISK-29933: cdr_adaptive_odbc: datetime type not supported
Reporter:Caesar (caesar305)Labels:
Date Opened:2022-02-22 20:47:21.000-0600Date Closed:2022-03-09 12:00:02.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:CDR/cdr_adaptive_odbc
Versions:18.9.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Centos 7Attachments:
Description:When using Mysql ODBC Connector (libmyodbc8w.so) and adaptive ODBC, there is an issue when writing to Datetime columns. In the Asterisk console, the following warning appears:

cdr_adaptive_odbc.c:731 odbc_log: Column type 9 (field 'asterisk:cdr:start') is unsupported at this time.

mysql> describe cdr;
+-------------+--------------+------+-----+---------+----------------+
| Field       | Type         | Null | Key | Default | Extra          |
+-------------+--------------+------+-----+---------+----------------+
| start       | datetime     | YES  |     | NULL    |                |


Proposal:

I see TIMESTAMP field type is already considered in the case within the cdr_adaptive_odbc.c, we can simply add Datetime to the switch.
Comments:By: Asterisk Team (asteriskteam) 2022-02-22 20:47:21.758-0600

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

By: Joshua C. Colp (jcolp) 2022-02-23 04:27:52.973-0600

Do you plan on providing a patch for this?

By: Caesar (caesar305) 2022-02-23 09:23:35.540-0600

Yes, I am waiting on the Contributor license approval.

By: Joshua C. Colp (jcolp) 2022-02-23 11:51:31.362-0600

Putting back into feedback. Once your agreement has been accepted, you can comment and this will go back into triage.

By: Asterisk Team (asteriskteam) 2022-03-09 12:00:01.518-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines