THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

James Luetkehoelter

Nearly any SQL topic presented at times in a slightly eclectic manner.

Now I've seen everything: A database with a Y10 bug...

...this is 100% serious. I have encountered a system that has a single digit year identifier that rolls every decade...I will now start working at McDonalds...
Published Friday, March 5, 2010 1:18 PM by James Luetkehoelter

Comments

 

Mr. E. said:

Does that make this the grandson to the Y2k bug?

Kids today...

March 5, 2010 2:25 PM
 

James Luetkehoelter said:

Yes - an issue that occured with primitive abaci :)

March 5, 2010 2:29 PM
 

ALZDBA said:

Finally we get to be colleagues ;-)

March 6, 2010 6:53 AM
 

Paul Nielsen said:

Perhaps they'll add a DecadeRolloverFlag bit field and set it true for the first 3-4 years of next decade so reports can determine the correct year?

March 6, 2010 12:45 PM
 

James Luetkehoelter said:

Actually Paul I'm pretty sure that's how decares are handled, but its with another randomly named integer field that looks like a lin item number or something. Seriously, I'm going to get a job at McDonalds as cooking fries where databases can exist only in my head in a wonderfully, elegently constructed fashion...

March 6, 2010 4:47 PM
New Comments to this post are disabled

About James Luetkehoelter

I am passionate about what I do - which is DBA, development, IT and IT business consulting. If you don't know me, haven't met me or have never heard me speak, I'm a little on the eccentric side. One attendee recently described me as being "over the top". Yup, that about says it - because I only speak on topics that I'm passionate about.
Privacy Statement