ovs-openflowd: Remove documentation for obsolete --mgmt-id option.

[openvswitch] / ovsdb / SPECS

diff --git a/ovsdb/SPECS b/ovsdb/SPECS
index f5d748c03cb5dd9f33903611adf56222066ebc04..cbd69defc3f62fc1b929815f1357ef9fb90f995f 100644 (file)
--- a/ovsdb/SPECS
+++ b/ovsdb/SPECS
@@ -101,6 +101,7 @@ is represented by <database-schema>, as described below.
     A JSON object with the following members:
 
         "columns": {<id>: <column-schema>, ...}   required
     A JSON object with the following members:
 
         "columns": {<id>: <column-schema>, ...}   required

+        "maxRows": <integer>                      optional

 
     The value of "columns" is a JSON object whose names are column
     names and whose values are <column-schema>s.
 
     The value of "columns" is a JSON object whose names are column
     names and whose values are <column-schema>s.


@@ -122,6 +123,13 @@ is represented by <database-schema>, as described below.
         the database process is stopped and then started again, each
         "_version" also changes to a new random value.
 
         the database process is stopped and then started again, each
         "_version" also changes to a new random value.
 

+    If "maxRows" is specified, as a positive integer, it limits the
+    maximum number of rows that may be present in the table.  This is
+    a "deferred" constraint, enforced only at transaction commit time
+    (see the "transact" request below).  If "maxRows" is not
+    specified, the size of the table is limited only by the resources
+    available to the database server.
+

 <column-schema>
 
     A JSON object with the following members:
 <column-schema>
 
     A JSON object with the following members:


@@ -243,6 +251,8 @@ over HTTP, for these reasons:
 
     * The JSON-RPC specification for HTTP transport is incomplete.
 
 
     * The JSON-RPC specification for HTTP transport is incomplete.
 

+We are using TCP port 6632 for the database JSON-RPC connection.
+

 The database wire protocol consists of the following JSON-RPC methods:
 
 list_dbs
 The database wire protocol consists of the following JSON-RPC methods:
 
 list_dbs


@@ -362,6 +372,11 @@ include at least the following:
         transaction), and this column is not allowed to be empty
         because its <type> has a "min" of 1.
 
         transaction), and this column is not allowed to be empty
         because its <type> has a "min" of 1.
 

+    "error": "constraint violation"
+
+        The number of rows in a table exceeds the maximum number
+        permitted by the table's "maxRows" value (see <table-schema>).
+

 If "params" contains one or more "wait" operations, then the
 transaction may take an arbitrary amount of time to complete.  The
 database implementation must be capable of accepting, executing, and
 If "params" contains one or more "wait" operations, then the
 transaction may take an arbitrary amount of time to complete.  The
 database implementation must be capable of accepting, executing, and