atom feed7 messages in org.apache.openjpa.usersRe: Query using timestamp version field
FromSent OnAttachments
kostellodonFeb 28, 2011 9:45 pm 
Michael DickMar 1, 2011 9:50 am 
kostellodonMar 1, 2011 1:57 pm 
Rick CurtisMar 1, 2011 2:16 pm 
kostellodonMar 1, 2011 2:36 pm 
Rick CurtisMar 2, 2011 7:20 am 
Rick CurtisMar 2, 2011 1:00 pm 
Subject:Re: Query using timestamp version field
From:kostellodon (dona@citi.com)
Date:Mar 1, 2011 2:36:48 pm
List:org.apache.openjpa.users

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.