In pursuit of what we can safely use as the infinite future on date comparisons:
scala> val t3 = new Timestamp(Long.MaxValue) t3: java.sql.Timestamp = 292278994-08-16 23:12:55.807
Yup - that’s year two hundred ninety two million and a lot.
by comparison here’s today.
t1: java.sql.Timestamp = 2011-05-04 22:58:11.658
scala> val t1 = new Timestamp(System.currentTimeMillis)
So sometime during August 16th, year 292,278,994, longs will no longer fit the current date and everyone still stuck on JVM 1.6 will be facing yet another Y2K style crisis. Good to know?
(I feel like there must be a joke in here somewhere… I’m open to suggestions :) )
