From da897f41cd795e325ec5ce773a70a819100bd26e Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Tue, 26 Jul 2011 10:24:17 -0700 Subject: 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. --- tests/test-ovsdb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests') diff --git a/tests/test-ovsdb.c b/tests/test-ovsdb.c index e151dd8b..1cdf69ae 100644 --- a/tests/test-ovsdb.c +++ b/tests/test-ovsdb.c @@ -1258,7 +1258,7 @@ do_execute(int argc OVS_UNUSED, char *argv[]) char *s; params = parse_json(argv[i]); - result = ovsdb_execute(db, params, 0, NULL); + result = ovsdb_execute(db, NULL, params, 0, NULL); s = json_to_string(result, JSSF_SORT); printf("%s\n", s); free(s); -- cgit v1.2.3