[Nepomuk] Review Request: DMM: Auto-commit after each data manipulation statement

[Sebastian Trueg]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107630/#review23306
-----------------------------------------------------------



services/storage/datamanagementmodel.cpp
<http://git.reviewboard.kde.org/r/107630/#comment17928>

    I think it should be 2 instead of 3. Or do we need logging?


- Sebastian Trueg


On Dec. 7, 2012, 7:51 p.m., Vishesh Handa wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/107630/
> -----------------------------------------------------------
> 
> (Updated Dec. 7, 2012, 7:51 p.m.)
> 
> 
> Review request for Nepomuk and Sebastian Trueg.
> 
> 
> Description
> -------
> 
>     With the ResourceMerger rewrite we no longer push one statement at a
>     time. We now push them in one large statement. This has been shown to
>     cause transaction deadlocks in virtuoso. It is recommended to set
>     log_enable( 3 ) in order to auto commit after each data manipulation
>     command.
>     
>     Ideally we should have proper transaction support and each command in
>     the data management model should be a separate transaction. However,
>     this will have to do until we figure out how to do that.
> 
> 
> Diffs
> -----
> 
>   services/storage/datamanagementmodel.cpp 4568e49 
> 
> Diff: http://git.reviewboard.kde.org/r/107630/diff/
> 
> 
> Testing
> -------
> 
> Still testing to see if I receive any transaction deadlocked errors.
> 
> 
> Thanks,
> 
> Vishesh Handa
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20121211/3f654435/attachment-0001.html>