> On Dec. 11, 2012, 9:57 a.m., Sebastian Trueg wrote: > > services/storage/datamanagementmodel.cpp, line 226 > > <http://git.reviewboard.kde.org/r/107630/diff/1/?file=97566#file97566line226> > > > > I think it should be 2 instead of 3. Or do we need logging?
http://docs.openlinksw.com/virtuoso/fn_log_enable.html The first bit is for logging, the second bit is for auto-commit after each statement. 3 => 10 (binary). Though, this patch doesn't seem to help. I still get the transaction deadlocked errors :/ - Vishesh ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/107630/#review23306 ----------------------------------------------------------- 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 > >
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
