Hmm, further information comes out. It seems to work with mine when I have
the field directly in my entity. In my standard case, I have a basic entity
that my standard entities extend. I have reduced by base entity to the
following:
@MappedSuperclass
public abstract class BasicEntity {
@Column(name="update_user")
private String updateUser;
@Column(name="update_user_namespace")
private String updateUserNamespace;
@Version
@Temporal(TemporalType.TIMESTAMP)
@Column(name="update_datetime")
private Timestamp updateDateTime;
@Column(name="insert_user")
private String insertUser;
@Column(name="insert_user_namespace")
private String insertUserNamespace;
@Temporal(TemporalType.TIMESTAMP)
@Column(name="insert_datetime")
private Timestamp insertDateTime;
...
}
If I extend this basic entity, I get the issue. If I don't use the base
class and have the updateDateTime directly in my class, the exception goes
away.
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Query-using-timestamp-version-field-tp6076165p6078987.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
