[asterisk-bugs] [JIRA] (ASTERISK-18252) queue_log mysql time column data format
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Jul 27 10:24:06 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-18252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-18252:
-------------------------------------
Target Release Version/s: 14.0.0
> queue_log mysql time column data format
> ---------------------------------------
>
> Key: ASTERISK-18252
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-18252
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Addons/res_config_mysql
> Affects Versions: 1.8.5.0
> Environment: centos 5.6
> Reporter: Gareth Blades
> Assignee: Rusty Newton
> Severity: Minor
> Target Release: 14.0.0
>
>
> I have configures mysql with the logging of queue information to the queue_log table using the schema supplied in the contrib directory.
> When I reload asterisk I get the following error :-
> res_config_mysql.c:1262 require_mysql: Realtime table queue_log at skycom: Column time cannot be a datetime
> Ok so maybe the information I saw that asterisk 1.8 stores teh date as a timestamp instead of an epoch was wrong so I change the data type to an int but I then get this :-
> Realtime table skycom at queue_log: column 'time' cannot be type 'int(11)' (need datetime)
> So its not allowing it to be datetime but when I set it to an int it tells me thats wrong and it should be set to datetime!
> What should it be set to?
> Can the error be fixed telling me to change it to a datetime when thats not acceptable.
> I know I can probably change it to a char() field but I am going to need to do a lot of searching on that value and storing it as a char is incredibly inefficient
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list