tag:blogger.com,1999:blog-497787815177352569.post5938525878290637867..comments2024-01-03T08:55:04.827-05:00Comments on SQL Anywhere: Let's play "Gotcha!" - Round OneBreck Carterhttp://www.blogger.com/profile/15975598564711761434noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-497787815177352569.post-77051128631688625372011-09-26T04:41:27.763-04:002011-09-26T04:41:27.763-04:00@Volker AKA Anonymous: That was a case of "BI...@Volker AKA Anonymous: That was a case of "BIGINT on the brain" :) Also, AFAIK TINYINT isn't an issue here, as the SELECT 255 + 1 showed, it's a SMALLINT (and INTEGER) thing. This behavior has been discussed before, but it always seems fresh when it bites anew.Breck Carterhttps://www.blogger.com/profile/15975598564711761434noreply@blogger.comtag:blogger.com,1999:blog-497787815177352569.post-46063225440123950222011-09-26T03:20:42.636-04:002011-09-26T03:20:42.636-04:00You got me!
FWIW, "SELECT CAST(32767 AS INT)...You got me!<br /><br />FWIW, "SELECT CAST(32767 AS INT) + 1" will do as well.<br /><br />In constrast, multiplication does not seem to stick to TINYINTs, e.g. SELECT 32767 * 4 does work.<br /><br />Volker Is Still PuzzledAnonymousnoreply@blogger.com