I'm doing this query within a unit test, and am using runtime enhancement via the javaagent.
I've tried this with both 1.2.2 and 2.1.0 and see the same index out of bounds exception in both cases. Either querying another timestamp field or removing the version annotation from the update field causes the exception to go away. Marking a field that is a Long as the version field also makes it go away, so it appears to be directly related to querying against a Timestamp version field. -- View this message in context: http://openjpa.208410.n2.nabble.com/Query-using-timestamp-version-field-tp6076165p6078869.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
