Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m considering storing some date values as ints.
i.e 201003150900
Excepting the fact that I lose any timezone information, is there anything else I should be concerned about with his solution?
Any queries using this column would be simple ‘where after or before’ type lookups.
i.e Where datefield is less than 201103000000 (before March next year).
currently the app is using MSSQL2005.
Any pointers to pitfalls appreciated.
Using a proper datetime datatype will give you more efficient storage (
smalldatetimeconsumes 4 bytes) and indexing, and will give you semantics that will be easier to develop against. You’d have to come up with a compelling argument to not use them.