We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When we declare table with unsigned tinyint, and store value larger than max value of corresponding SIGNED type, negative number is return.
CREATE TABLE t1 (ts TIMESTAMP, f1 TINYINT UNSINGED, f2 SMALLINT UNSIGNED, f3 INT UNSIGNED, f4 BIGINT UNSIGNED);
INSERT INTO t1 (ts, f1, f2, f3, f4) VALUES (NOW, 255, 65535, 4294967295, POW(2, 64) - 1);
Just like the mysql-connector-j way, map TINY_UNSIGNED to Integer, SMALLINT_UNSIGNED to Integer, INT_UNSIGNED to Long, BIGINT_UNSIGNED to BigInteger.
UTINYINT
Short
Byte
USMALLINT
Integer
UINT
Long
UBIGINT
BigInteger
The text was updated successfully, but these errors were encountered:
fix: restful metadata testcase (taosdata#150)
9f242de
fix: restful result set getByte/Int/Short invalid on MIN value (taosd…
cd39483
…ata#150)
Successfully merging a pull request may close this issue.
Senario:
When we declare table with unsigned tinyint, and store value larger than max value of corresponding SIGNED type, negative number is return.
Reproduce
Solution:
Just like the mysql-connector-j way, map TINY_UNSIGNED to Integer, SMALLINT_UNSIGNED to Integer, INT_UNSIGNED to Long, BIGINT_UNSIGNED to BigInteger.
UTINYINT
should useShort
instead ofByte
.USMALLINT
should useInteger
instead ofShort
.UINT
should useLong
instead ofInteger
.UBIGINT
should useBigInteger
instead ofLong
The text was updated successfully, but these errors were encountered: