Michael Hodgdon wrote: > I am curious how religiously people stay true to using data types for MS SQL > Server. I know some of these stretch to other RDBMS's, however, I would > like to know what people in industry think. What type of general rules of > thumb do people follow when planning data types for a data store? For > instance Money, Numeric, varchar, int, bigint ... I think you get the > point.
Money: never, it is not a predefined type in SQL. Use NUMERIC instead. "CHARACTER, CHARACTER VARYING, CHARACTER LARGE OBJECT, BINARY LARGE OBJECT, BIT, BIT VARYING, NUMERIC, DECIMAL, INTEGER, SMALLINT, FLOAT, REAL, DOUBLE PRECISION, BOOLEAN, DATE, TIME, TIMESTAMP, and INTERVAL" says the SQL standard (time and timestamp may or may not have a timezone). Of those, I have reservations with the large object types and with intervals. Although they are standardized, few databases support them fully and you might run into issues. I also have reservations with using timezones. But for some applications, you just need them. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
