From 53a32616a799553901dd73e2ab32412e3b5e8881 Mon Sep 17 00:00:00 2001
From: jackfoxy <jackfoxy@gmail.com>
Date: Sun, 18 Jun 2023 14:26:39 -0700
Subject: [PATCH] docs

---
 docs/ref-ch07-transform.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/ref-ch07-transform.md b/docs/ref-ch07-transform.md
index 4334b8f..aa0b8ef 100755
--- a/docs/ref-ch07-transform.md
+++ b/docs/ref-ch07-transform.md
@@ -9,6 +9,7 @@ The `<transform>` statements provides a means of chaining commands on `<table-se
   <cmd>
   [ INTO <table>
     | <transform-op> [ ( ] <cmd> [ ) ]
+    | <tee-op> <set-op> [ ( ] <cmd> [ ) ]
   ] [ ...n ]
   [ AS OF { NOW
           | <timestamp>
@@ -76,6 +77,11 @@ NOTE: rule for dividing union `<row-type>`s TBD.
   | TEE
   | MULTEE
 ```
+```
+<tee-op> ::=
+  TEE
+  | MULTEE
+```
 
 `<pass-thru-op>`s make the left resulting `<table-set>` available for consumption by the next `<cmd>` in the `<transform>`. The right side of the statement cannot be nested. The left `<table-set>` can be consumed by `*`, in which case column identifiers and `<row-type>` column alignments from the left `<cmd>` apply, or a list of column aliases, in which case all columns produced by the left `<cmd>` must be included in the order produced.  (See the definition of `<table-set>` in the Introduction.) In other words the `<row-type>` of the left `<table-set>` applies when consumed by the right `<cmd>`.