Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.1.31, 10.1.33, 10.2.15
-
None
-
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
|
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
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}} |
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 bq. collation-server = utf8_bin}} ========== |
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 bq. collation-server = utf8_bin}} ========== |
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 bq. collation-server = utf8_bin}} ========== |
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 bq. collation-server = utf8_bin}} ========== |
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}} ========== |
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}} ========== |
I cannot insert into a VEC table any values as soon as I declare a column "unsigned".
Example: *Step 1)* {code:java} CREATE TABLE test ( mycol tinyint *unsigned* ) DEFAULT CHARSET=utf8 COLLATE=utf8_bin engine=CONNECT table_type=VEC file_name='test_.vec' ; {code} *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 ========== |
Description |
I cannot insert into a VEC table any values as soon as I declare a column "unsigned".
Example: *Step 1)* {code:java} CREATE TABLE test ( mycol tinyint *unsigned* ) DEFAULT CHARSET=utf8 COLLATE=utf8_bin engine=CONNECT table_type=VEC file_name='test_.vec' ; {code} *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 ========== |
I cannot insert into a VEC table any values as soon as I declare a column "unsigned".
Example: *Step 1)* {code:java} CREATE TABLE test ( mycol tinyint *unsigned* ) DEFAULT CHARSET=utf8 COLLATE=utf8_bin engine=CONNECT table_type=VEC file_name='test_.vec' ; {code} *Step 2)* {code:java} insert into test values(1) ; {code} *Result)* {code:java} ERROR 1296 (HY000): Got error 122 'Non matching Value types' from CONNECT {code} 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": {code:java} character-set-server = utf8 collation-server = utf8_bin {code} |
Description |
I cannot insert into a VEC table any values as soon as I declare a column "unsigned".
Example: *Step 1)* {code:java} CREATE TABLE test ( mycol tinyint *unsigned* ) DEFAULT CHARSET=utf8 COLLATE=utf8_bin engine=CONNECT table_type=VEC file_name='test_.vec' ; {code} *Step 2)* {code:java} insert into test values(1) ; {code} *Result)* {code:java} ERROR 1296 (HY000): Got error 122 'Non matching Value types' from CONNECT {code} 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": {code:java} character-set-server = utf8 collation-server = utf8_bin {code} |
I cannot insert into a VEC table any values as soon as I declare a column "unsigned".
Example: *Step 1)* {code:java} CREATE TABLE test ( mycol tinyint unsigned ) DEFAULT CHARSET=utf8 COLLATE=utf8_bin engine=CONNECT table_type=VEC file_name='test_.vec' ; {code} *Step 2)* {code:java} insert into test values(1) ; {code} *Result)* {code:java} ERROR 1296 (HY000): Got error 122 'Non matching Value types' from CONNECT {code} 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": {code:java} character-set-server = utf8 collation-server = utf8_bin {code} |
Affects Version/s | 10.2.15 [ 23006 ] |
Fix Version/s | 10.1 [ 16100 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Assignee | Olivier Bertrand [ bertrandop ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
issue.field.resolutiondate | 2018-06-28 21:52:43.0 | 2018-06-28 21:52:43.309 |
Fix Version/s | 10.0.36 [ 22916 ] | |
Fix Version/s | 10.1.35 [ 23116 ] | |
Fix Version/s | 10.3.8 [ 23113 ] | |
Fix Version/s | 10.2.16 [ 23110 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 87215 ] | MariaDB v4 [ 154358 ] |
Fixed in version 10.2.16.