History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: SES-218
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Arjohn Kampman
Reporter: Arjohn Kampman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sesame

Native Sail's NamespaceStore doesn't reset '_contentsChanged' field to false upon commit or rollback

Created: 14/Jan/06 12:41 PM   Updated: 06/Feb/06 10:19 PM
Component/s: Native Sail
Affects Version/s: 1.1, 1.2, 1.1-RC1, 1.1-RC2, 1.1.1, 1.1.2, 1.1.3, 1.2-RC1, 1.2-RC2, 1.2.1, 1.2.2, 1.2.3
Fix Version/s: 1.2.4


 Description   
Quote by Nick Edgar on simile mailing list:

"...While tracing through the SesamePerfTest, I noticed that the _contentsChanged flag is not cleared in NamespaceStore._commitTransaction or rollbackTransaction, so a subsequent commitTransaction without a startTransaction would end up nulling out the main table and map."

Although this scenario never occurs in the current code, the flag should be reset upon commit or rollback.

 All   Comments   Change History      Sort Order:
There are no comments yet on this issue.