Hi David, seems like a bug. I will write a test case to check this out.
By the way currently the ObjectCache does not support the 'readonly' feature. Means it is possible to cache and lookup an object with changed 'readonly' fields. regards, Armin ----- Original Message ----- From: "David Warnock" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 30, 2003 6:20 AM Subject: OJB is updating read-only columns > Hi, > > I have a field like this > > <field-descriptor > name="rowTimestamp" > column="RowTimestamp" > jdbc-type="TIMESTAMP" > access="readonly" > /> > > This is because the database sets this column, all I want to do is read > it (to display the time the row was last saved). > > BUT Ojb is trying to insert a value for this column. > > I have not set the value anywhere (so it should be null anyway). The > insert statement is: > > INSERT INTO EmailAddresses > (EmailAddressId,RowVersion,RowUserId,RowTimestamp,ContactId,EmailAddress ) > VALUES ( '104', '1', '1', '', '101', '44' ) > > It seems to me that Ojb should leave the readonly fields out of insert > and update statements. > > Is this a bug? > > Thanks > > Dave > -- > David Warnock, Sundayta Ltd. http://www.sundayta.com > iDocSys for Document Management. VisibleResults for Fundraising. > Development and Hosting of Web Applications and Sites. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
