From 7fe4d20553fdbe7b9cd0649ad1d5b3267e8adeb7 Mon Sep 17 00:00:00 2001 From: ShiroOnigami23 Date: Mon, 20 Apr 2026 02:12:20 +0530 Subject: [PATCH] doc: fix typos in CQL SELECT tuple-notation explanation --- doc/cql3/CQL.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/cql3/CQL.textile b/doc/cql3/CQL.textile index 6efcea6dde5f..85feb9731ecf 100644 --- a/doc/cql3/CQL.textile +++ b/doc/cql3/CQL.textile @@ -1252,7 +1252,7 @@ It is also possible to "group" @CLUSTERING COLUMNS@ together in a relation using bc(sample). SELECT * FROM posts WHERE userid='john doe' AND (blog_title, posted_at) > ('John''s Blog', '2012-01-01') -will request all rows that sorts after the one having "John's Blog" as @blog_tile@ and '2012-01-01' for @posted_at@ in the clustering order. In particular, rows having a @post_at <= '2012-01-01'@ will be returned as long as their @blog_title > 'John''s Blog'@, which wouldn't be the case for: +will request all rows that sorts after the one having "John's Blog" as @blog_title@ and '2012-01-01' for @posted_at@ in the clustering order. In particular, rows having a @posted_at <= '2012-01-01'@ will be returned as long as their @blog_title > 'John''s Blog'@, which wouldn't be the case for: bc(sample). SELECT * FROM posts WHERE userid='john doe' AND blog_title > 'John''s Blog' AND posted_at > '2012-01-01'