On 20/06/12 09:23, Ian Dickinson wrote:
Thanks Andy. By re-ordering actions and the transactions in my code,
I've resolved the root problem.
I know you said you're hoping to remove this restriction on models and
transactions at some point via view graphs, but in the meantime would it
be worth adding more diagnostic info to the "** unexpected" error message?
Ian
The message is in fact not related to the problem - it just happens to
trigger an internal check and that's the first one it hits. I guess it
should be an exception like IllegalStateException.
NodeTableTrans needs a complete rewrite to be safe(r) for data in the
situation of external failure (JVM crash, machine power loss).
Good news is that I have some code to do viewgraphs - but I don't want
to start on that until their is a period of stability. A quick
(re)release to fix the Fuseki logged exception seems important to me.
Andy
