s3:registry: update the seqnum in the subkey cache at the end of regval_store_keys
commit3a42d5612837908a64d54fecab7bfeccf605fa66
authorMichael Adam <obnox@samba.org>
Wed, 11 Apr 2012 14:02:44 +0000 (11 16:02 +0200)
committerKarolin Seeger <kseeger@samba.org>
Fri, 22 Jun 2012 19:41:32 +0000 (22 21:41 +0200)
tree11ea6af4cb3d610b46ed992079a80f1d0c56f4dc
parentca56054a5a62b96904642580f83f1a871b607ffb
s3:registry: update the seqnum in the subkey cache at the end of regval_store_keys

The purpose is to prevent next reads from going to disk.

Note that this will currently only be effective with local tdbs, not
with ctdb: For tdb, store and delete bump the seqnum while transaction
commit does not. For ctdb, transaction commit bumps the seqnum, while
store and delete don't... This needs fixing (in ctdb).
(cherry picked from commit 16d83149c1b5620598edd37bbd1a73bebec82b6e)
(cherry picked from commit 96f08f6d43cb9bebda175efd5719ca15549a5b99)
source3/registry/reg_backend_db.c