> >> Is there any way in the peer model to query
> >> whether an update was successful at all (even if
> >> it did not update any records)? Same thing for
> >> a delete?
It seems this is done by catching a possible Exception
thrown by doUpdate, doInsert and/or doDelete. It might
be nice to throw more specific exceptions in this case.
> >> Is there any way in the peer model to query for
> >> how many records were updated after a doUpdate()
> >> was issued? Same thing for doDelete()?
>
> What have you tried? Take a look at the source code.
Ok, I did take a look at the source code, and couldn't
find anything that looks like a way of finding out how
many records were affected by doUpdate, doDelete or
doInsert. It is possible that with the current methods,
doInsert always returns 1 (success) or throws an exception
(failure), but doUpdate and doDelete could definitely
affect more than one record. Any further hints? Is this
supported at all in Turbine? Is it necessary to go deeper
down into Village to answer this question? If yes, should
this functionality be exported so that it is accessible
directly via Turbine?
> -jon
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
