diff options
| author | Ben Pfaff <blp@ovn.org> | 2018-09-06 19:30:11 -0700 |
|---|---|---|
| committer | Ben Pfaff <blp@ovn.org> | 2018-10-03 18:13:45 -0700 |
| commit | 64107d596747179436cb7a4bd6ab31ba277d136b (patch) | |
| tree | 5cef317b691facfffa8d585e4415bafa964e3db8 /Documentation/ref | |
| parent | fcaba95e26d695f59379cd1b930d8243d5b551c0 (diff) | |
| download | openvswitch-64107d596747179436cb7a4bd6ab31ba277d136b.tar.gz | |
condition: Reject <, <=, >=, > with optional scalar against empty set.
When relational comparisons against optional scalars were introduced, it
was meant to work only when the right-hand side of the comparison was a
scalar, not the empty set. The implementation wasn't that picky. This
commit fixes the problem.
CC: Terry Wilson <twilson@redhat.com>
Fixes: 09e256031a62 ("ovsdb: Allow comparison on optional scalar types")
Signed-off-by: Ben Pfaff <blp@ovn.org>
Acked-by: Justin Pettit <jpettit@ovn.org>
Diffstat (limited to 'Documentation/ref')
| -rw-r--r-- | Documentation/ref/ovsdb-server.7.rst | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst index 22b335bab..14c7da8e9 100644 --- a/Documentation/ref/ovsdb-server.7.rst +++ b/Documentation/ref/ovsdb-server.7.rst @@ -455,9 +455,10 @@ form:: For <condition>, RFC 7047 only allows the use of ``!=``, ``==``, ``includes``, and ``excludes`` operators with set types. Open vSwitch 2.4 and later extend <condition> to allow the use of ``<``, ``<=``, ``>=``, and ``>`` operators with -columns with type "set of 0 or 1 integer" and "set of 0 or 1 real". These -conditions evaluate to false when the column is empty, and otherwise as -described in RFC 7047 for integer and real types. +a column with type "set of 0 or 1 integer" and an integer argument, and with +"set of 0 or 1 real" and a real argument. These conditions evaluate to false +when the column is empty, and otherwise as described in RFC 7047 for integer +and real types. <condition> is specified in Section 5.1 in the RFC with the following change: A condition can be either a 3-element JSON array as described in the RFC or a |