New answers tagged datatypes
We do this in our data warehouse. It's because decimal has a fixed precision and float isn't accurate past a certain number of decimal places. We need to retain the most accurate value extracted from the source as we are summing over 100 million rows and the rounding would put our figures out. However if you've got a fixed number of decimal places, then go ...
You should not be concerned on how SQL Server stores the data. For now, you should use the TIME data type and if you want the 12 hour format, then convert it in the front end application or during SELECT statement using CAST() or CONVERT()
As of MySQL v5.6.3 they added support for INET6_ATON and INET6_NOTA that will take care of IPv4 and IPv6 addresses. But they no longer store it as an integer. IPv6 returns a varbinary(16) and and IPv4 returns a varbinary(4). http://dev.mysql.com/doc/refman/5.6/en/miscellaneous-functions.html#function_inet6-aton
Top 50 recent answers are included