Okay, to answer my own question I found the source for working dogs at http://share.whichever.com/
and it seems like the doUpdate() method is not setting the records for saving via update. Although having changed that still does not solve my problem. It appears I will have to delve deeper into working dogs. CHEERS> SAM Sam Joseph wrote: > Hi All, > > I'm having a strange experience with the doUpdate method. I've been > using some code in a XXXPeer class, like this: > > Criteria x_crit = new Criteria(); > x_crit.addJoin(UriPeer.URI_ID, UriTriplePeer.URI_ID); > x_crit.addJoin(UriTriplePeer.URI_TRIPLE_ID,EventPeer.URI_TRIPLE_ID); > x_crit.add(USER_ID, p_user.getUserId()); > x_crit.add(UriPeer.URI_ID, p_uri.getUriId()); > Criteria x_update = new Criteria(); > x_update.add(SHARED,Boolean.FALSE); > doUpdate(x_crit,x_update); > which seems to be working, i.e. the column labelled SHARED is updated > to false in the appropriate table. Actually I only got it to work for > multiple records by modifying BasePeer so as not to throw an exception > when a row already had a false value in that column. > > The problem I now have is that this operation also seems to be > resetting a date column in the same table. It seems like the update > operation is automatically resetting the date column, maybe even at > the level of the workingdogs.villiage code, which I am currently > struggling to find the source for. > > Can anyone offer any useful advice? > > Thanks in advance. > > CHEERS> SAM > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
