dynamobi-build
commented
12 years ago [author="jpham", created="Thu, 28 Sep 2006 13:17:05 -0500 (GMT-05:00)"]
The exact message of the last trace was:
Sep 28, 2006 1:17:48 PM net.sf.farrago.db.FarragoDbSession rollbackImpl
INFO: rollback
Even if a value is returned by the result set and the assertEquals fails, then the test case also hangs. So it might either be related to the test harness, or something about how the test harness calls into Jdbc.
[reporter="jpham", created="Thu, 28 Sep 2006 13:05:31 -0500 (GMT-05:00)"] (Old title was) FarragoJdbcTest.testDataTypes hangs if there is a resultSet error)
I'm not sure whether this is problem is limited to the test harness or if it could occur outside test situations.
When one fetches data through a Jdbc result set, it usually goes through org.eigenbase.util14.AbstractResultSet.java. One uses method such as getDate(), which in turn relies on methods like toDate(). The method toDate() casts a raw object, which may be of any type, into the desired type, such as Date.
In general, the methods are written according to this idiom:
if (o instanceof TypeA) {
...
} else if (o instance of TypeB) {
...
} else {
throw new ConversionError(...)
}
If an unexpected raw data type is encountered, and it cannot be casted to the desired type, then a ConversionError is thrown. Since it is such a common pattern, I expect that it must be well tested. But somehow, when I was missing a required conversion, I was getting a hang, with the last message sent to the trace being something to the effect of "Database... rollbackImpl".