MySQL Changes in 5.1.0-beta1?

I have a pretty simple dashboard that is using MySQL as a datasource which seems to have broke in the latest beta. I looked in the release notes but couldn’t find much that would have affected it?

One of my queries is:

SELECT
UNIX_TIMESTAMP(date_created) as time_sec,
id as value, ‘Tickets’ as metric
FROM tickets

Formatted as time series, I now get this message: Value column must have numeric datatype, column: value type: *int32 value: 0xc42060b338

Running this cmd in MySQL generates just numeric values?

Hi,

Can you please share your MySql version number and schema of your tickets table? Are you using format as time series or table?

Please see link for mysql related changes in v5.1 beta.

Marcus

Hi, MySQL is v5.6.29 still…guessing that might be the issue?

Not necessarily. Please include your table schema and I will try to reproduce. Think this will give you the correct output SHOW CREATE TABLE tickets.

Marcus

I stripped out some items that weren’t needed to simplify;

tickets CREATE TABLE tickets (
id int(11) NOT NULL AUTO_INCREMENT,
agent_id int(11) DEFAULT NULL,
date_created datetime NOT NULL,
date_resolved datetime DEFAULT NULL,
date_archived datetime DEFAULT NULL,
date_status datetime NOT NULL,
ref varchar(100) NOT NULL,
PRIMARY KEY (id),
UNIQUE KEY ref_idx (ref),
KEY IDX_54469DF43414710B (agent_id),
KEY date_created_idx (date_created),
) ENGINE=InnoDB AUTO_INCREMENT=2748 DEFAULT CHARSET=utf8

Thanks.

Confirmed as a bug. Issue created here and should be fixed to v5.1 stable release.

Marcus

Sounds good, thank you!