Skip to content

Commit b1b2e54

Browse files
devkevMichael Paik
authored andcommitted
Visually highlight the warning about using $min xor $max
Following up from DOCS-4015, the second paragraph in the "$min without $max" and "$max within $min" sections should be more noticable, since it is warning the user of hazardous usage that is best avoided.
1 parent 91cff88 commit b1b2e54

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

source/includes/fact-query-min-max.rst

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,9 @@ should avoid normal query planning. Instead they construct an index scan where
33
the index bounds are explicitly specified by the values given in
44
:operator:`min` and :operator:`max`.
55

6-
If one of the two boundaries is not specified, then the query plan will be
7-
an index scan that is unbounded on one side. This may degrade performance
8-
compared to a query containing neither operator, or one that uses both
9-
operators to more tightly constrain the index scan.
6+
.. warning::
7+
8+
If one of the two boundaries is not specified, then the query plan will be
9+
an index scan that is unbounded on one side. This may degrade performance
10+
compared to a query containing neither operator, or one that uses both
11+
operators to more tightly constrain the index scan.

0 commit comments

Comments
 (0)