s3:registry:db: update the value container seqnum after storing/deleting to prevent...
commit4367071f62d2994f1d3d4f33d45fcd6b4c7bec26
authorMichael Adam <obnox@samba.org>
Wed, 11 Apr 2012 13:38:29 +0000 (11 15:38 +0200)
committerAndreas Schneider <asn@samba.org>
Wed, 25 Apr 2012 12:31:11 +0000 (25 14:31 +0200)
treeb510762bd4110c3990a16fa6a7dafb26609ce319
parent8c7047b0e7b1ee25a6a5535cf495c9afded2d924
s3:registry:db: update the value container seqnum after storing/deleting to prevent next read from going to disk if possible

Note that this will currently only be effective in the local TDB implementation.
For CTDB, this wont work since seqnum currently works differently there (needs
fixing): For tdb, store and delete operations bump the db seqnum, while
transaction commits don't. For ctdb, the seqnum is bumped by the transaction
commit but not by store and delete operations.

Signed-off-by: Andreas Schneider <asn@samba.org>
source3/registry/reg_backend_db.c