A small change that has been made to java.sql.Timestamp to add a local compareTo() that just calls its superclass (java.util.Date), rather than not declaring it at all and letting the superclass do the job implicitly. This has apparently been done to fix BugID 4227983 but has the side-effect of stopping them implicitly comparing a Date to a Timestamp, and doing so at Runtime, not at compile time =O(

The text for Date.compareTo(Object) in the javadocs from 1.3.1 onwards state:
     
     "Compares this Date to another Object. If the Object is a Date, this
     function behaves like compareTo(Date). Otherwise, it throws a
     ClassCastException (as Dates are comparable only to other Dates)."
     
The same text for Timestamp says:
     
     "Compares this Timestamp to another Object. If the Object is a Date,
     this function behaves like compareTo(Timestamp). Otherwise, it
     throws a ClassCastException (as Timestamps are comparable only to
     other Timestamps)."
   
It seems quite clear to me that this is a typo, and that first "Date"
should also have been search&replaced to Timestamp. This is
what led the customer to believe that they were doing an OK thing in
their code in 1.3.x, and it did indeed work back then =O{

Whether the javadocs are correct or not, though, the functionality provided by this addition is definately not - see the Comments section.