Community
There was a rash of stories last week about assorted web sites not coping with February 29th or leap years in general. You'd think by now this kind of thing would have been sorted out - we did after all see off the Y2K bug and the rules of the Gregorian calendar are quite well established and have been in use for some time.
Interesting to see then that Microsoft's SQL Server 2008 community technology preview was brought down by the same leap year bug just 48 hours after Microsoft unveiled it. This in the same week they admitted one in Exchange 2007. Oops.
This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.
Joris Lochy Product Manager at Intix | Co-founder at Capilever
31 December
Carlo R.W. De Meijer Owner and Economist at MIFSA
30 December
Prashant Bhardwaj Innovation Manager at Crif
29 December
Kaustuv Ghosh CEO at Nxtgencode
Welcome to Finextra. We use cookies to help us to deliver our services. You may change your preferences at our Cookie Centre.
Please read our Privacy Policy.