The Timestamp type field in MySQL is updated automatically whenever the record is touched, so it doesn't even need a set method, but if I don't have one it complains on deployment. Its not the set that is giving me issues but the get. In the database, none of the timestamp fields are null.
-Scott
Pinaki Poddar
<[EMAIL PROTECTED]
rg> To
[email protected]
10/30/2008 03:29 cc
PM
Subject
Re: Timestamp always returns null
Please respond to
[EMAIL PROTECTED]
che.org
The following code seems to be the cause:
> public void setValueChangeDate(Timestamp date) {
> //
> }
How about the following instead?
public void setValueChangeDate(Timestamp date) {
this.valueChangeDate = date;
}
--
View this message in context:
http://n2.nabble.com/Timestamp-always-returns-null-tp1400326p1400376.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
