Deployed 9612d42 with MkDocs version: 1.6.0

abstractions/index.html

@@ -373,6 +373,15 @@
     </span>
   </a>
 
+</li>
+
+          <li class="md-nav__item">
+  <a href="#sqlnode" class="md-nav__link">
+    <span class="md-ellipsis">
+      SQLNode
+    </span>
+  </a>
+
 </li>
 
       </ul>
@@ -608,6 +617,15 @@
     </span>
   </a>
 
+</li>
+
+          <li class="md-nav__item">
+  <a href="#sqlnode" class="md-nav__link">
+    <span class="md-ellipsis">
+      SQLNode
+    </span>
+  </a>
+
 </li>
 
       </ul>
@@ -684,6 +702,11 @@ <h3 id="graphreducenode">GraphReduceNode</h3>
 <h3 id="dynamicnode">DynamicNode</h3>
 <p>A dynamic node is any node that is instantiated without defined method 
 definitions.  This is useful for doing automated feature engineering.</p>
+<h3 id="sqlnode">SQLNode</h3>
+<p>A SQL node is an abstraction for SQL dialects and backends.  This allows us to
+go beyond the dataframe API that a typical <code>GraphReduceNode</code> or <code>DynamicNode</code> 
+is built for and leverage a number of SQL backends.  There is more detail
+about how to use these in <a href="../tutorial_sql_dialects/">the SQL backends tutorial</a>.</p>
 <h2 id="edge">Edge</h2>
 <p>An edge is a relationship between two nodes.  This is typically a foreign key.  For 
 example if we had a <code>customers</code> table and <code>orders</code> table we would add an edge between the 

tutorial_sql_dialects/index.html

@@ -499,6 +499,15 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#more-examples" class="md-nav__link">
+    <span class="md-ellipsis">
+      More examples
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -550,6 +559,15 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#more-examples" class="md-nav__link">
+    <span class="md-ellipsis">
+      More examples
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -673,6 +691,15 @@ <h2 id="sql-operations">SQL operations</h2>
 </span><span id="__span-2-46"><a id="__codelineno-2-46" name="__codelineno-2-46" href="#__codelineno-2-46"></a>        <span class="n">WHERE</span> <span class="n">ord_ts</span> <span class="o">&gt;</span> <span class="s1">&#39;2022-12-01&#39;</span>
 </span><span id="__span-2-47"><a id="__codelineno-2-47" name="__codelineno-2-47" href="#__codelineno-2-47"></a>        <span class="n">GROUP</span> <span class="n">BY</span> <span class="n">ord_customer_id</span>
 </span></code></pre></div>
+<h2 id="more-examples">More examples</h2>
+<p>There are more examples on <a href="https://github.com/wesmadrigal/GraphReduce">github</a></p>
+<ul>
+<li><a href="https://github.com/wesmadrigal/GraphReduce/blob/master/examples/sql_dialects_ex1.ipynb">example 1</a></li>
+<li><a href="https://github.com/wesmadrigal/GraphReduce/blob/master/examples/sql_dialects_ex2.ipynb">example 2</a></li>
+<li><a href="https://github.com/wesmadrigal/GraphReduce/blob/master/examples/sql_dialects_ex3.ipynb">example 3</a></li>
+<li><a href="https://github.com/wesmadrigal/GraphReduce/blob/master/examples/sql_dialects_ex4.ipynb">example 4 automated feature engineering</a></li>
+<li><a href="https://github.com/wesmadrigal/GraphReduce/blob/master/examples/sql_dialects_ex4.ipynb">example 5 automated feature engineering con't</a></li>
+</ul>
 
 
 

tutorial_swapping_compute/index.html

@@ -609,6 +609,7 @@
 
 
 <h1 id="swapping-compute-layers">Swapping compute layers</h1>
+<p>Full code <a href="https://github.com/wesmadrigal/GraphReduce/blob/master/examples/tutorial_ex4.ipynb">here</a></p>
 <p>There are API differences between a lot of compute layers
 but between <code>pandas</code> and <code>dask</code> the API is mostly the same.  This
 makes swapping between these two compute layers a breeze.</p>