temp

Author: kay-kim

doc/user/data/examples/create-table/example_mysql_table.yml

@@ -0,0 +1,90 @@
+- name: "create-table"
+  description: |
+    To create new **read-only** tables from a source, in the `CREATE TABLE FROM
+    SOURCE` statement, specify the table in the publication using the
+    `REFERENCE` field.
+
+    The following example creates **read-only** tables `items` and `orders` that
+    are populated from the corresponding `items` and `orders` tables from the
+    MySQL source `mz_source`.
+
+    {{< note >}}
+
+    - Although the example creates the tables with the same names as the
+    upstream tables, the tables in Materialize can have names that differ from
+    the referenced table names.
+
+    - For supported MySQL data types, refer to [supported
+    types](#upstream-sources-and-supported-data-types).
+
+    - You can create multiple tables that reference the same upstream table.
+
+    {{< /note >}}
+
+  code: |
+    /* This example assumes:
+      - In the upstream MySQL, you have:
+        - Enabled GTID-based binlog replication
+        - Defined a replication user and password with the appropriate access.
+      - In Materialize,
+        - You have defined the connection to the upstream MySQL.
+        - You have used the connection to create a source; e.g.,
+          CREATE SECRET mysql_password AS '<replication user password>'; -- substitute
+          CREATE CONNECTION mysql_connection TO MYSQL (
+            HOST '<hostname>',          -- substitute
+            USER <replication user>,    -- substitute
+            PASSWORD SECRET mysql_password
+            -- [, <network security configuration> ]
+          );
+
+          CREATE SOURCE mz_source
+          FROM MYSQL CONNECTION mysql_connection;
+    */
+
+    CREATE TABLE items
+    FROM SOURCE mz_source(REFERENCE public.items)
+    ;
+    CREATE TABLE orders
+    FROM SOURCE mz_source(REFERENCE public.orders)
+    ;
+
+- name: "show-tables"
+  description: |
+    To verify that the table has been created, you can run [`SHOW
+    TABLES`](/sql/show-tables/) to list all tables in the current [schema](/sql/namespaces/#namespace-hierarchy):
+  code: |
+    SHOW TABLES;
+  results: |
+    The results should include the tables `items` and `orders`:
+
+    ```hc {hl_lines="3-4"}
+    | name        | comment |
+    | ----------- | ------- |
+    | items       |         |
+    | orders      |         |
+    ```
+
+- name: "show-columns"
+  description: |
+    Inspect the table columns using the [`SHOW COLUMNS`](/sql/show-columns/) command:
+  code: |
+    SHOW COLUMNS FROM items;
+    SHOW COLUMNS FROM orders;
+  results: |
+    The results should display information on the table columns. The types
+    should match those from the upstream table.
+
+    For the list of supported PostgreSQL data types, refer to [supported
+    types](#upstream-sources-and-supported-data-types).
+
+- name: "read-from-table"
+  code: |
+    SELECT * FROM items;
+
+- name: "create-view-from-tables"
+  code: |
+    CREATE VIEW orders_view AS
+    SELECT o.*,i.price,o.quantity * i.price as subtotal
+    FROM orders as o
+    JOIN items as i
+    ON o.item = i.item;

doc/user/data/examples/create-table/example_postgres_table.yml

@@ -45,10 +45,10 @@
     */
 
     CREATE TABLE items
-    FROM SOURCE mz_source(REFERENCE items)
+    FROM SOURCE mz_source(REFERENCE public.items)
     ;
     CREATE TABLE orders
-    FROM SOURCE mz_source(REFERENCE orders)
+    FROM SOURCE mz_source(REFERENCE public.orders)
     ;
 
 - name: "show-tables"
@@ -75,8 +75,7 @@
     SHOW COLUMNS FROM orders;
   results: |
     The results should display information on the table columns. The types
-    should match those from the upstream table with the exception of those that
-    were explicitly converted to `text` in the `WITH` clause.
+    should match those from the upstream table.
 
     For the list of supported PostgreSQL data types, refer to [supported
     types](#upstream-sources-and-supported-data-types).

…t/postsgres-unsupported-type-handling.md …nt/postgres-unsupported-type-handling.mddoc/user/shared-content/postsgres-unsupported-type-handling.md renamed to doc/user/shared-content/postgres-unsupported-type-handling.md doc/user/shared-content/postsgres-unsupported-type-handling.md renamed to doc/user/shared-content/postgres-unsupported-type-handling.md

@@ -1,6 +1,7 @@
 Replicating tables that contain **unsupported data types** is possible via the
-[`TEXT COLUMNS` option]. When decoded as `text`, the specified
-columns will not have the expected PostgreSQL type features. For example:
+[`TEXT COLUMNS`](/sql/create-table/#syntax). When decoded as `text`, the
+specified columns will not have the expected PostgreSQL type features. For
+example:
 
 * [`enum`]: When decoded as `text`, the resulting `text` values will
   not observe the implicit ordering of the original PostgreSQL `enum`; instead,