Issue 376 in simal: Persistence of data in TDB

[si...@googlecode.com]

Status: Accepted
Owner: sander.v...@oucs.ox.ac.uk
Labels: Type-Defect Priority-High

New issue 376 by sander.v...@oucs.ox.ac.uk: Persistence of data in TDB
http://code.google.com/p/simal/issues/detail?id=376

There seem to be issues related to persisting the data reported on the list
[1]. See issue 344 [2] for earlier problems.

Data should not be just be persisted when shutting down the JVM. Even when
the application would crash data put in hours before should still be there.
This seems to be not the case but needs to be tested more thoroughly.

We need to understand (and then document) how Jena takes care of these
issues.

[1]
http://groups.google.com/group/simal-contributors/browse_thread/thread/c7300f3629d9764d
[2] http://code.google.com/p/simal/issues/detail?id=344

[si...@googlecode.com]

Updates:
Owner: ---
Labels: -Priority-High Priority-Critical Milestone-0.3 Usability

Comment #1 on issue 376 by ross.gardler: Persistence of data in TDB
http://code.google.com/p/simal/issues/detail?id=376

(No comment was entered for this change.)

[si...@googlecode.com]

Updates:
Labels: Slotted
Blockedon: 416

Comment #2 on issue 376 by sander.v...@gmail.com: Persistence of data in TDB

[si...@googlecode.com]

Comment #3 on issue 376 by sander.v...@oucs.ox.ac.uk: Persistence of data
in TDB
http://code.google.com/p/simal/issues/detail?id=376

This issue was updated by revision r2240.

There was something fundamentally wrong with how we save the data which is
related to a workaround I had to create because Wicket works with Lists
whereas we have Sets everywhere. As a result changes are not correctly
persisted. Working on a better solution.