From c5bc99b8cb3e9e2f238a0c2374470fd9af595295 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Mon, 13 Mar 2006 17:18:03 +0000 Subject: [PATCH] tweak --- doc/build/content/sqlconstruction.myt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/content/sqlconstruction.myt b/doc/build/content/sqlconstruction.myt index f4c5f6d2a8..12fe1576ca 100644 --- a/doc/build/content/sqlconstruction.myt +++ b/doc/build/content/sqlconstruction.myt @@ -593,7 +593,7 @@ FROM addresses WHERE addresses.address_id IN

The sql package supports embedding select statements into other select statements as the criterion in a WHERE condition, or as one of the "selectable" objects in the FROM list of the query. It does not at the moment directly support embedding a SELECT statement as one of the column criterion for a statement, although this can be achieved via direct text insertion, described later.

- <&|doclib.myt:item, name="scalar", description="Scalar Column Queries"&> + <&|doclib.myt:item, name="scalar", description="Scalar Column Subqueries"&>

Subqueries can be used in the column clause of a select statement by specifying the scalar=True flag:

<&|formatting.myt:code &> <&formatting.myt:poplink&>select([table2.c.col1, table2.c.col2, select([table1.c.col1], table1.c.col2==7, scalar=True)]) -- 2.47.2