Hello.
The behaviour of UNSIGNED BIGINT was correct on my Win2k Professional.
Do you use a mysql command line client or other client software?
mysql> create table bu(a bigint unsigned);
Query OK, 0 rows affected (0.20 sec)
mysql> insert into bu values('18446744073709551615');
Query OK, 1 row affected (0.06 sec)
mysql> select * from bu;
+----------------------+
| a |
+----------------------+
| 18446744073709551615 |
+----------------------+
1 row in set (0.00 sec)
mysql> select version();
+-----------+
| version() |
+-----------+
| 4.1.10-nt |
+-----------+
1 row in set (0.00 sec)
[snip]
I am testing against MySQL 4.1 current release on Windows and there seems to
be a fault with unsigned bigint datatypes.
Using a BIGINT UNSIGNED datatype, the maximum value that will be accepted on
insert query is 9223372036854775807 , which is actually the published
maximum for signed Bigints.
Also - with any other unsigend integer, an input value which exceeds the
maximum will be corrected and be set to the maximum value (eg. input 70000
to a smallint unsigned and you get 65535). However, with BigInt only the
resulting value is set to zero.
Is this a genuine fault or am misunderstanding something?
Tim Hayes"Tim Hayes" <[EMAIL PROTECTED]> wrote:
[snip]
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Gleb Paharenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
