summaryrefslogtreecommitdiff
path: root/ovsdb/ovsdb-tool.c
diff options
context:
space:
mode:
authorBen Pfaff <blp@nicira.com>2011-07-26 10:24:17 -0700
committerBen Pfaff <blp@nicira.com>2011-07-26 16:50:09 -0700
commitda897f41cd795e325ec5ce773a70a819100bd26e (patch)
tree23635409122e1f95c3a73af8b8f50b8495ab0ef6 /ovsdb/ovsdb-tool.c
parente317253b1391c7b0a84c8dd51eaf1f3cc16eff56 (diff)
downloadopenvswitch-da897f41cd795e325ec5ce773a70a819100bd26e.tar.gz
ovsdb: Implement a "lock" feature in the database protocol.
This provides clients a way to coordinate their access to the database. This is a voluntary, not mandatory, locking protocols, that is, clients are not prevented from modifying the database unless they cooperate with the locking protocol. It is also not related to any of the ACID properties of database transactions. It is strictly a way for clients to coordinate among themselves. The following commit will introduce one user.
Diffstat (limited to 'ovsdb/ovsdb-tool.c')
-rw-r--r--ovsdb/ovsdb-tool.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/ovsdb/ovsdb-tool.c b/ovsdb/ovsdb-tool.c
index 822eb6b2e..74dfa5a5b 100644
--- a/ovsdb/ovsdb-tool.c
+++ b/ovsdb/ovsdb-tool.c
@@ -311,7 +311,7 @@ transact(bool read_only, const char *db_file_name, const char *transaction)
check_ovsdb_error(ovsdb_file_open(db_file_name, read_only, &db, NULL));
request = parse_json(transaction);
- result = ovsdb_execute(db, request, 0, NULL);
+ result = ovsdb_execute(db, NULL, request, 0, NULL);
json_destroy(request);
print_and_free_json(result);