|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 12:01 PM
Points: 2,677,
Visits: 2,273
|
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 2:04 AM
Points: 1,342,
Visits: 1,946
|
|
I notice that the ODBC datetime format is very strict!
select { ts '2008-09-21 12:34:56' } is OK.select { ts '2008-9-21 12:34:56' } produces a conversion error!
Derek
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 12:01 PM
Points: 2,677,
Visits: 2,273
|
|
I guess thats a good thing in a cross-technology standard!
Kev
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 8:48 AM
Points: 2,440,
Visits: 714
|
|
I wasn't aware of the ODBC datatype. Good question. Answer was obvious after the following worked:
DECLARE @ts timestamp, @dt as datetime
set @dt = {ts '2008-09-21 15:53:00'}
But, does the timestamp update from the code above? If not, how would this work?
Jamie
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Yesterday @ 3:57 PM
Points: 2,550,
Visits: 17,372
|
|
Nicely written! Excellent job coming up with some answers that sound good if you haven't used a timestamp before, yet leaving the correct answer clearly on it's own.
|
|
|
|
|
SSCarpal Tunnel
       
Group: General Forum Members
Last Login: Wednesday, May 22, 2013 1:35 AM
Points: 4,789,
Visits: 1,336
|
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Sunday, May 19, 2013 11:16 PM
Points: 1,061,
Visits: 1,151
|
|
really nice question
|
|
|
|