From 1bee1c22cbef0b39baae45ecfc9f25bc8723d99b Mon Sep 17 00:00:00 2001 From: Jens Schauder Date: Wed, 8 Jan 2025 09:30:49 +0100 Subject: [PATCH] Refining QBE documentation. Adds a configurable limitation about collection support in Query By Example. Closes: #3226 --- src/main/antora/modules/ROOT/pages/query-by-example.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/main/antora/modules/ROOT/pages/query-by-example.adoc b/src/main/antora/modules/ROOT/pages/query-by-example.adoc index f3f27cb8c..45590079c 100644 --- a/src/main/antora/modules/ROOT/pages/query-by-example.adoc +++ b/src/main/antora/modules/ROOT/pages/query-by-example.adoc @@ -1,3 +1,7 @@ +ifndef::support-qbe-collection[] +:support-qbe-collection: true +endif::[] + [[query-by-example]] = Query by Example @@ -36,6 +40,9 @@ Query by Example is well suited for several use cases: Query by Example also has several limitations: * No support for nested or grouped property constraints, such as `firstname = ?0 or (firstname = ?1 and lastname = ?2)`. +ifeval::[{support-qbe-collection} != true] +* No support for matching collections or maps. +endif::[] * Store-specific support on string matching. Depending on your databases, String matching can support starts/contains/ends/regex for strings. * Exact matching for other property types.