From e349856296143036217758a654f7b57113334c11 Mon Sep 17 00:00:00 2001 From: Kevin Pulo Date: Fri, 13 Mar 2015 18:18:35 +1100 Subject: [PATCH] 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. --- source/includes/fact-query-min-max.rst | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/source/includes/fact-query-min-max.rst b/source/includes/fact-query-min-max.rst index 34a9d8e2359..e9a789dd756 100644 --- a/source/includes/fact-query-min-max.rst +++ b/source/includes/fact-query-min-max.rst @@ -3,7 +3,9 @@ should avoid normal query planning. Instead they construct an index scan where the index bounds are explicitly specified by the values given in :operator:`min` and :operator:`max`. -If one of the two boundaries is not specified, then the query plan will be -an index scan that is unbounded on one side. This may degrade performance -compared to a query containing neither operator, or one that uses both -operators to more tightly constrain the index scan. +.. warning:: + + If one of the two boundaries is not specified, then the query plan will be + an index scan that is unbounded on one side. This may degrade performance + compared to a query containing neither operator, or one that uses both + operators to more tightly constrain the index scan.