From 63d2dfec36976ac4a1368709b106f48b54853420 Mon Sep 17 00:00:00 2001
From: ADBond <48208438+ADBond@users.noreply.github.com>
Date: Wed, 15 Jan 2025 12:48:41 +0000
Subject: [PATCH] brief note on ColumnExpression benefit

---
 docs/api_docs/column_expression.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/api_docs/column_expression.md b/docs/api_docs/column_expression.md
index 797fbe9537..09eddcd97b 100644
--- a/docs/api_docs/column_expression.md
+++ b/docs/api_docs/column_expression.md
@@ -16,6 +16,7 @@ However, there may be situations where you don't wish to derive a new column, pe
 
 This is where a `ColumnExpression` may be used. It represents some SQL expression, which may be a column, or some more complicated construct,
 to which you can also apply zero or more transformations. These are lazily evaluated, and in particular will not be tied to a specific SQL dialect until they are put (via [settings](./settings_dict_guide.md) into a linker).
+This can be particularly useful if you want to write code that can easily be switched between different backends.
 
 ??? warning "Term frequency adjustments"
     One caveat to using a `ColumnExpression` is that it cannot be combined with term frequency adjustments.