Fred van Engen wrote: > SELECT 2147483648*2147483648*4 returns 0. > SELECT 2147483648*2147483648*2 returns -9223372036854775808. > SELECT 2147483648*2147483648*2-1 returns 9223372036854775807. > > The same problem in most programming languages. What do other DBMS do > and what do the SQL standards say? I really don't know. Neither do I.
>> Ordinary, UPDATE or INSERT would do one record at a time. > INSERT INTO test(id, myint) VALUES (1,2147483647), (2,2147483648); > The second is out-of-bounds. Should the first be revoked? Given behaviour in some other situations: yes... >> BTW INSERT -or REPLACE- do croak about misfits while using FKs and >> then do not process any field -and none of the other records, if you >> used an record set- > Great. That's InnoDB, which could do the same for each of the earlier > examples. People might expect that from transactioned tables. Sorry, forgotten to make explicit in the examples, I have 'default-table-type=innodb' configured. That has been applied to all sample codes. I'ld leave the subject to rest for now. HansH -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
