![]() |
|
|
#1 | ||
|
Death Herald
Join Date: Nov 2000
Location: Le stelle la notte sono grandi e luminose nel cuore profondo del Texas
|
You learn something new everyday
We are testing a new app for one of our customers, and ran across a strange date issue when inserting data from a form into the database. SQL Server's datetime data type doesn't accept dates before 1/1/1753. Here's why:
What is the significance of 1/1/1753 in SQL Server? - Stack Overflow
__________________
Thinkin' of a master plan 'Cuz ain't nuthin' but sweat inside my hand So I dig into my pocket, all my money is spent So I dig deeper but still comin' up with lint |
||
|
|
|
|
|
#2 |
|
Grizzled Veteran
Join Date: May 2003
Location: Ashburn, VA
|
That is so nerdy. And pretty interesting!
/tk
__________________
GO TERPS! https://www.flickr.com/photos/terpkristin https://twitter.com/terpkristin |
|
|
|
|
|
#3 |
|
Coordinator
Join Date: Dec 2004
Location: San Diego via Sausalito via San Jose via San Diego
|
Just use COBOL.
__________________
I'm no longer a Chargers fan, they are dead to me Coming this summer to a movie theater near you: The Adventures of Jedikooter: Part 4 |
|
|
|
|
|
#4 |
|
College Starter
Join Date: Oct 2000
|
Wow thanks for sharing this tidbit.
__________________
... |
|
|
|
|
|
#5 |
|
Coordinator
Join Date: Dec 2004
Location: San Diego via Sausalito via San Jose via San Diego
|
The SQL thing I did not know about (very interesting), however, the changing of the calendars back in the mid 1700's, I've known about for a long time.
__________________
I'm no longer a Chargers fan, they are dead to me Coming this summer to a movie theater near you: The Adventures of Jedikooter: Part 4 |
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|