[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6779?page=c... ] Steve Ebersole commented on HHH-6779: ------------------------------------- For sake of completeness, Sybase defines its {{TINYINT}} datatype as 0-128; SQL Server defines it as 0-255. Neither of which match with the JDBC {{TINYINT}} definition. Neither define a data type {{NUMBER}} afaik. They use the ANSI term {{DECIMAL}} (or {{NUMERIC}}, as a synonym). Unfortunately there does not seem to be a direct corollary to the JDBC {{TINYINT}} type in Sybase or SQL Server. Both {{SMALLINT}} and {{DECIMAL(3,0)}} represented wasted storage space as far as storing a Java {{byte}} value. However, I agree that this is the only viable solution *as far as our tests go*. However we still have a potential issue there with existing apps trying to store out of range values into columns defined as type {{TINYINT}}. This fix will not change that behavior. This fix just makes the column data type bigger moving forward. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6779?page=c... ] Strong Liu commented on HHH-6779: --------------------------------- okay, smallint takes 2 byte but numeric(3,0) takes 5 bytes, so i think smallint win -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira