Re: OJB is updating read-only columns

2003-08-14 Thread David Warnock
Jakob, Sorry for the delay in checking this. We have upgraded to rc4 and the problem is fixed. Many thanks Dave do you still have problems with updated readonly fields ? jakob David Warnock wrote: Jakob, imo there have been no changes affecting read-write attributes for some time. Thank

Re: OJB is updating read-only columns

2003-06-17 Thread David Warnock
Jakob, do you still have problems with updated readonly fields ? We have not had chance to upgrade OJB and re-test yet. I am away al week so am not sure yet when I will be able to test this. Dave -- David Warnock, Sundayta Ltd. http://www.sundayta.com iDocSys for Document Management. VisibleResu

Re: OJB is updating read-only columns

2003-06-16 Thread Jakob Braeuchi
hi david, do you still have problems with updated readonly fields ? jakob David Warnock wrote: Jakob, imo there have been no changes affecting read-write attributes for some time. Thanks, as soon as I get this rush out of the way I am going to look into this because Armin's test is working

Re: OJB is updating read-only columns

2003-06-01 Thread David Warnock
Jakob, imo there have been no changes affecting read-write attributes for some time. Thanks, as soon as I get this rush out of the way I am going to look into this because Armin's test is working (and I checked the p6spy log). But currently on our application (rc2, I think) it is not. Hopefull

Re: OJB is updating read-only columns

2003-06-01 Thread Jakob Braeuchi
hi david, imo there have been no changes affecting read-write attributes for some time. jakob David Warnock wrote: Armin, Great! I will submit a patch for this later today. Given your test is working either something is wrong with our application or maybe some recent ojb change has affe

Re: OJB is updating read-only columns

2003-05-31 Thread David Warnock
Armin, Great! I will submit a patch for this later today. Given your test is working either something is wrong with our application or maybe some recent ojb change has affected it. So I will instead get us upgraded to the latest and greatest ojb and see if that solves our problem. Thanks for

Re: OJB is updating read-only columns

2003-05-31 Thread Armin Waibel
Good argument! ;-) regards, Armin - Original Message - From: "Jakob Braeuchi" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Friday, May 30, 2003 6:04 PM Subject: Re: OJB is updating read-only columns > hi armin, > > rea

Re: OJB is updating read-only columns

2003-05-31 Thread Jakob Braeuchi
t: Friday, May 30, 2003 11:59 AM Subject: Re: OJB is updating read-only columns Armin, seems like a bug. I will write a test case to check this out. I am certain it is a bug. In looking at it I have realised that my earlier patch which added support for update-lock="false

Re: OJB is updating read-only columns

2003-05-30 Thread Armin Waibel
Great! - Original Message - From: "David Warnock" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Friday, May 30, 2003 11:59 AM Subject: Re: OJB is updating read-only columns > Armin, > > > seems like a bug. I will write

Re: OJB is updating read-only columns

2003-05-30 Thread David Warnock
Armin, seems like a bug. I will write a test case to check this out. I am certain it is a bug. In looking at it I have realised that my earlier patch which added support for update-lock="false" was incomplete. Both access="readonly" and update-lock="false" need to be checked in the various Sql*

Re: OJB is updating read-only columns

2003-05-30 Thread Armin Waibel
e - 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 > > name="rowTimestamp" > colu

OJB is updating read-only columns

2003-05-30 Thread David Warnock
Hi, I have a field like this 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 stateme