Please sign in to comment.
Bug #20535517 INCORRECT HANDLING OF UNSIGNED NOT NULL INTEGERS IN
INNODB_MEMCACHED PROBLEM 1)Column attribute can be both IB_COL_UNSIGNED and IB_COL_NOT_NULL, but in the code many times we are checking unsigned attribute in column meta data using "==" operator which will lead to wrong results. 2) When setting up the field value for unsigned integer we are calling innodb_api_write_uint64() without checking the column length which causes assert in innodb_api_write_uint64() if length is less than 8. FIX 1) Check if the unsigned attribute in a column is set by using binary & operator. 2) Check column length before calling innodb_api_write_uint64() for unsigned integer [ rb#9043 and rb#9054 Approved by Jimmy ]
- Loading branch information...
Showing with 12 additions and 11 deletions.