tdb2: use tdb->flags & TDB_RDONLY instead of tdb->read_only for TDB1 code.
authorRusty Russell <rusty@rustcorp.com.au>
Wed, 31 Aug 2011 05:58:16 +0000 (15:28 +0930)
committerRusty Russell <rusty@rustcorp.com.au>
Wed, 31 Aug 2011 05:58:16 +0000 (15:28 +0930)
commit4dc29a338fadeac805b369b4b0851c02f1b152c7
treec6259529674bc0c46e8d7d6f38ee106ad33d0d9b
parent3e46dde21261966941469a6c75e1b45cd2d26324
tdb2: use tdb->flags & TDB_RDONLY instead of tdb->read_only for TDB1 code.

There's also a semantic change here: for tdb1, being read-only meant no
locking, and it was an error to try to lock a r/o database.  For TDB2, you'd
need to specify TDB_NOLOCK, which suppresses locking silently.
ccan/tdb2/tdb1_check.c
ccan/tdb2/tdb1_io.c
ccan/tdb2/tdb1_lock.c
ccan/tdb2/tdb1_open.c
ccan/tdb2/tdb1_private.h
ccan/tdb2/tdb1_summary.c
ccan/tdb2/tdb1_tdb.c
ccan/tdb2/tdb1_transaction.c
ccan/tdb2/tdb1_traverse.c
ccan/tdb2/test/run-tdb1-3G-file.c