[MDEV-16167] "connect" storage engine using table type VEC: cannot use "unsigned" types Created: 2018-05-14  Updated: 2018-10-28  Resolved: 2018-06-28

Status: Closed
Project: MariaDB Server
Component/s: Data types, Storage Engine - Connect
Affects Version/s: 10.1.31, 10.1.33, 10.2.15
Fix Version/s: 10.0.36, 10.1.35, 10.2.16, 10.3.8

Type: Bug Priority: Minor
Reporter: Stefano Assignee: Olivier Bertrand
Resolution: Fixed Votes: 0
Labels: None
Environment:

Gentoo Linux, amd64, Xeon E31270, gentoo-sources kernel 4.14.40



 Description   

I cannot insert into a VEC table any values as soon as I declare a column "unsigned".
Example:

Step 1)

CREATE TABLE test (
  mycol tinyint unsigned
)
DEFAULT CHARSET=utf8 COLLATE=utf8_bin
engine=CONNECT table_type=VEC file_name='test_.vec'
;

Step 2)

insert into test values(1)
;

Result)

ERROR 1296 (HY000): Got error 122 'Non matching Value types' from CONNECT

Tried with different integer types ("integer", "bigint"), but the result is always the same.
Am I doing something wrong?
Docs (https://mariadb.com/kb/en/library/connect-data-types/#unsigned-numeric-types) state that unsigned should not be a problem (from what I understood mariadb 10.1.31 & .34 should be using a connect-engine more recent than 1.01.0010)
Thx

p.s.: explicitly used collate & charset as I have in "my.cnf":

character-set-server = utf8
collation-server = utf8_bin



 Comments   
Comment by Olivier Bertrand [ 2018-06-26 ]

Fixed in version 10.2.16.

Comment by Stefano [ 2018-07-14 ]

It works perfectly - thanks a lot )))

Generated at Thu Feb 08 08:26:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.