From 85ae6c96d31d3d12e88cf989c90120418856fce7 Mon Sep 17 00:00:00 2001 From: Xiaokui Shu Date: Mon, 8 Jan 2024 13:44:53 -0500 Subject: [PATCH] fix code typo in doc:faq:sqlexpressions on `in_()` (#10845) (cherry picked from commit 66cb236856cb458f34b5aa1e4f2ec737e1e45f76) --- doc/build/faq/sqlexpressions.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/faq/sqlexpressions.rst b/doc/build/faq/sqlexpressions.rst index 051d5cca20..7a03bdb036 100644 --- a/doc/build/faq/sqlexpressions.rst +++ b/doc/build/faq/sqlexpressions.rst @@ -319,7 +319,7 @@ known values are passed. "Expanding" parameters are used for string can be safely cached independently of the actual lists of values being passed to a particular invocation of :meth:`_sql.ColumnOperators.in_`:: - >>> stmt = select(A).where(A.id.in_[1, 2, 3]) + >>> stmt = select(A).where(A.id.in_([1, 2, 3])) To render the IN clause with real bound parameter symbols, use the ``render_postcompile=True`` flag with :meth:`_sql.ClauseElement.compile`: -- 2.47.2