Do I have to convert dates for a .NET developer so they can capture ms?
Or is there a method they are suppose to be using
I had to remove my modified date check to check for data collisions because they can't pass back microseconds.
What's the dealDepending on which of the .NET languages is being used, and in most of them which data type is being used, temporal data can be stored to the day, second, or true millisecond (which is actually more precise than SQL Server can store).
The short answer becomes something like: If you want absolute portability, convert and send them text (character) data. If they are using C#, C++, or VB then they just have to choose the correct data type. Most of the other .NET languages can store times to millieconds, but depending on the language that can be a pain in the patoot.
-PatP|||This dodges the obvious bullet about most developers not being able to even get a date, much less handle one! ;)
-PatP|||i thought this was a craigslist post.|||OK, CONVERT it is
And why is sql server limited in th MS category?
Something about clock speed?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment