RE: svn commit: r1371831 / The idea behind the workqueue
From: Bert Huijben <bert_at_qqmail.nl>
Date: Tue, 21 Aug 2012 13:37:52 +0200
> -----Original Message-----
Delayed review, as I didn't feel like typing this on my phone a few weeks ago, and I don't think this had to be solved soon.
As a temporary api I don't see a problem with this, but I would recommend *not* using workqueue items for just updating wc.db. Especially if you can do the same work in the same db transaction as the primary operation. The workqueue's task is just keeping the database and in-working copy data in sync.
Delaying the operation to a workqueue operation leaves the database in an 'in-between' stable-states and running the workqueue for such an operation requires at least 3 additional database transactions before the database is stable again.
And not using a workqueue operation also makes it easier to change the way we handle this in the future. Once we release a Subversion version with some workqueue support 'all future versions' should support running this workqueue item.
For now I would recommend just going on the way you started... we can fix this before branching.
This is an archived mail posted to the Subversion Dev mailing list.