Viewing 7 posts - 1 through 7 (of 7 total)
trboyden (6/23/2016)
Luis Cazares (6/23/2016)
It is a valid date.What do you mean by "the correct error checking functions"?
http://www.w3schools.com/sql/sql_dates.asp
http://www.w3schools.com/sql/func_convert.asp
https://msdn.microsoft.com/en-us/library/ms187347.aspx ( ISDATE() Function)
https://technet.microsoft.com/en-us/library/ms179465(v=sql.105).aspx ( Handling Database Engine Errors )
http://sqlmag.com/t-sql/t-sql-best-practices-part-2 (See datetime best practices...
June 23, 2016 at 11:21 am
trboyden (6/23/2016)
Jeff Moden (6/23/2016)
No need for the sarcasm. You made an incorrect statement that newbies would misinterpret and I made sure they weren't mislead.
Shifting gears to the subject at...
June 23, 2016 at 9:13 am
trboyden (6/21/2016)
Jeff Moden (6/20/2016)
trboyden (6/20/2016)
SQL Server expects the date to be passed in as "2016-06-20 00:00:00"
That's not true at all. SQL Server will take a couple dozen date/time formats...
June 21, 2016 at 7:04 am
Ken Hiatt (6/20/2016)
June 21, 2016 at 3:18 am
LC
I quite agree that the table should not be using the varchar (20) field to store the date values.
What surprised me was how sql server interpreted the wrong data...
June 20, 2016 at 2:11 pm
trboyden (6/20/2016)
June 20, 2016 at 8:34 am
As expected a lot of people will be stuck on the fact that the code was wrong in the first place. That is not without question. However, the interesting thing...
June 20, 2016 at 7:20 am
Viewing 7 posts - 1 through 7 (of 7 total)