Bug 52763 - Data Source admin/item map data: do not flush during each update operation right away
Summary: Data Source admin/item map data: do not flush during each update operation ri...
Alias: None
Product: SyncEvolution
Classification: Unclassified
Component: SyncEvolution (show other bugs)
Version: unspecified
Hardware: All All
: medium enhancement
Assignee: SyncEvolution Community
QA Contact:
Depends on:
Reported: 2010-04-19 19:58 UTC by SyncEvolution Community
Modified: 2018-10-13 12:42 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Patrick Ohly 2012-07-29 18:36:00 UTC

---- Reported by jingke.zhang@intel.com 2010-04-19 19:58:32 +0000 ----

This is from http://bugzilla.moblin.org/show_bug.cgi?id=8022

   Description  From  Chen Congwu   2009-11-14 06:23:12 PST   (-) [reply]

It looks like synthesis code does not guarantee flush() be called after
updating the admin data and item map table. As a workaround, we flush the
update during each update operation. 

Patrick wrote:
It might be possible to put the flush() elsewhere. For the admin data it
seemed easier to flush right away. I also wasn't quite sure about the
Synthesis engine's expectations: if we crash and never reach that later
flush, would the local state still be consistent?

--- Bug imported by patrick.ohly@gmx.de 2012-07-29 20:36 UTC  ---

This bug was previously known as _bug_ 1011 at https://bugs.meego.com/show_bug.cgi?id=1011
Comment 1 GitLab Migration User 2018-10-13 12:42:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/SyncEvolution/syncevolution/issues/85.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.