Bug #76802 InnoDB Memcached Plugin unsigned int(10) stores wrong values

• Submitted: 23 Apr 2015 3:57
• Modified: 18 Jan 2019 13:51
• Reporter: Alexander Panyutin
• Status: No Feedback
• Category: MySQL Server: Memcached
• Severity: S2 (Serious)
• Version: 5.6.43
• OS: Linux (CentOS release 6.5 (Final), x64)
• CPU Architecture: Any
• Tags: InnoDB Memcached Plugin

[23 Apr 2015 3:57] Alexander Panyutin

Description:
I've used InnoDB Memcached Plugin for version 5.6.

When I've describe in innodb_memcache.containers table fields described as UNSIGNED INT(10) DEFAULT 0 - it stores wrong integer value in memcached ( but key values used right values - I have next columns - `id`, `amount`, `locked` - all of them - UNSIGNED INT(10) DEFAULT 0, `id` is a primary auto_increment )

When I change column definition to INT(10) DEFAULT 0 ( I've mean signed ) - right integer values stored.

How to repeat:
see description.

[5 May 2015 4:16] Alexander Panyutin

ENUM also stores wrong values, for example:
in table:
`status` ENUM('canceled','finished','started') NOT NULL DEFAULT 'started',
in `containers` of `innodb_memcache`
`value_columns`='amount|status'
in fact from memcached:
250|-107
where 250 is correct, but -107 means 'finished'

[18 Dec 2018 13:51] MySQL Verification Team

Hi,

Thank you for your report.

We are not capable of repeating your test case as is. We would require the entire test case which should include:

* The setup of the MemCached Plugin
* Definitions of the tables
* The exact INSERT command
* The command that retrieves values from this Plugin

Thanks in advance.

[19 Jan 2019 1:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".