You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Sergey Kozlov (JIRA)" <ji...@apache.org> on 2015/03/11 17:09:38 UTC

[jira] [Created] (IGNITE-468) Schema load utility assigns incorrect java types

Sergey Kozlov created IGNITE-468:
------------------------------------

             Summary: Schema load utility assigns incorrect java types
                 Key: IGNITE-468
                 URL: https://issues.apache.org/jira/browse/IGNITE-468
             Project: Ignite
          Issue Type: Bug
    Affects Versions: sprint-2
         Environment: MySQL DB server
            Reporter: Sergey Kozlov
            Assignee: Alexey Kuznetsov
             Fix For: sprint-2


MySQL Db servers allows follow number data types:
1. Unsigned numbers:
{noformat}
mysql> create table t1 (a1 tinyint unsigned, a2 tinyint signed, b1 smallint unsigned, b2 smallint signed, c1 mediumint unsigned, c2 mediumint signed,
d1 int unsigned, d2 int signed, e1 bigint unsigned, e2 bigint signed);
Query OK, 0 rows affected (0.41 sec)
{noformat}
But the utility assigns for unsigned types same type as for signed one, e.g. 
SmallInt unsigned (0..255) to Java.lang.Byte (-128 ... +127)

2.Allow to set for bit columns (limited to 64):
{noformat}
mysql> create table t3 (a bit(64));
Query OK, 0 rows affected (0.49 sec)

mysql> insert into t3 values(b'0000000001111101010');
Query OK, 1 row affected (0.09 sec)

mysql> select bin(a) from t3;
+------------+
| bin(a)     |
+------------+
| 1111101010 |
+------------+
1 row in set (0.02 sec)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)