Post reply

WTF?? concatenating Date and time varchar fields messes up the milliseconds!!

  • July 1, 2010 at 1:24 pm

    #1187875

    mberry 51447 (7/1/2010)

    Still doesnt help with Milliseconds.

    So basically I am SOL without 2008:(

    I am looking more into what my customer needs this for. Just comparing, that would be find to compare as int but display, no way.

    Please read my previous post!

    BIGINT would help you to store datetime with milliseconds and also work great in comparisons and sorting. If you want to present this value as date/time back to the GUI, YES you will need to do some reformatting into string. Actually, there is no huge difference of how you will store it, same as for VARCHAR, BIGINT will not allow you to use datetime functions and as soon as you will try to cast to datetime your precious milliseconds will be lost. However, storing it in BIGINT will be faster for sorting and comparison (and index, if you need one, will take less space :-D)

    _____________________________________________
    "The only true wisdom is in knowing you know nothing"
    "O skol'ko nam otkrytiy chudnyh prevnosit microsofta duh!":-D
    (So many miracle inventions provided by MS to us...)

    How to post your question to get the best and quick help[/url]

  • July 16, 2010 at 11:22 am

    #1194249

    We are going forward using BIGINT and using it for comparison purposes but storing it in other columns...

    Thanks Ladies and Gents!

Viewing 2 posts - 16 through 16 (of 16 total)

You must be logged in to reply to this topic. Login to reply