From 369ae401b0759a98f9ae2f94d1576ce5f63cd196 Mon Sep 17 00:00:00 2001 From: baluyotraf Date: Fri, 22 Mar 2024 22:13:36 +0100 Subject: [PATCH] Fix typo on blog updates and altqq --- docs/stories/posts/20240322-blog-updates-and-altqq/content.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/stories/posts/20240322-blog-updates-and-altqq/content.md b/docs/stories/posts/20240322-blog-updates-and-altqq/content.md index 8aeef43..9e77b87 100644 --- a/docs/stories/posts/20240322-blog-updates-and-altqq/content.md +++ b/docs/stories/posts/20240322-blog-updates-and-altqq/content.md @@ -34,7 +34,7 @@ Alternative Queries (altqq). Alternative Queries also allows you to manage your query parameters. For example, for ODBC databases, `pyodbc` does not allow named parameter. If means that to reuse queries, one needs to make note of the parameters, as they must -be in order. For example +be in order. For example: ```python query1 = """SELECT * from "Users" where "Id" = ?""" @@ -44,7 +44,7 @@ full_query = f"{query1} UNION ALL {query2}" parameters = [uuid4(), "Arie"] ``` -The simple above looks simple, but if `query1` takes 3 parameters, and the +The code above looks simple, but if `query1` takes 3 parameters, and the `full_query` reuses 3-5 existing queries, the scenario becomes more complex. Even in this case, there is a possibility to define `parameters` as `["Arie", uuid4()]` if one is not careful.