superdb-mcp 1.3.1 → 1.3.3

package/dist/index.js

@@ -17,7 +17,7 @@ const __dirname = dirname(__filename);
 const docsDir = join(__dirname, '../docs');
 const server = new Server({
     name: 'superdb-mcp',
-    version: '1.3.1',
+    version: '1.3.3',
 }, {
     capabilities: {
         tools: {},

package/docs/tutorials/chess-tiebreaks.md

@@ -8,6 +8,10 @@ web: "https://chrismo.github.io/superkit/_build/tutorials/chess-tiebreaks/"
 
 # Chess Tiebreaks
 
+SuperDB isn't limited to JSON — it can ingest and transform plain text just as
+easily. This tutorial demonstrates parsing raw text input using `grok` patterns,
+reshaping records, and aggregating results to answer a real question.
+
 PGN (Portable Game Notation) is a plain text format for recording chess games.
 Each game has metadata in bracketed lines like `[White "LastName, FirstName"]`
 followed by the moves. Here we'll parse a tournament's PGN file to find players

package/docs/tutorials/joins.md

@@ -21,8 +21,8 @@ web: "https://chrismo.github.io/superkit/_build/tutorials/joins/"
 
 Left Join (Left Only + Inner Joins — where clause required to eliminate inner joins)
 
-Note: In 0.1.0, `select *` now includes columns from both sides. The right table's
-columns get a `_1` suffix to avoid name collisions, and unmatched values are
+`select *` includes columns from both sides. The right table's columns get a
+`_1` suffix to avoid name collisions, and unmatched values are
 `error("missing")`.
 ```mdtest-command
 super -s -c "select * from za.sup as za

package/docs/tutorials/subqueries.md

@@ -92,7 +92,7 @@ super -s -c '
 {id:4,date:"2025-02-28",foo:9}
 ```
                                  
-`super` also supports SQL syntax, and these subqueries work:
+`super` also supports SQL syntax, and these subqueries work[^1]:
 
 ```mdtest-command
 super -s -c '
@@ -220,6 +220,9 @@ super -s -c '
 {id:4,date:"2025-02-28",score:9,name:"Sprocket"}
 ```
 
+[^1]: SQL subqueries that reference files re-read the file for each subquery,
+    which increases CPU usage and wall time compared to the piped approach.
+
 # as of versions
 
 ```mdtest-command

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superdb-mcp",
-  "version": "1.3.1",
+  "version": "1.3.3",
   "description": "MCP server for SuperDB - execute SuperSQL queries, version detection, and embedded documentation",
   "type": "module",
   "main": "dist/index.js",

package/docs/tutorials/moar_subqueries.md

@@ -1,32 +0,0 @@
----
-name: moar-subqueries
-description: "Additional subquery patterns including fork and full sub-selects."
-superdb_version: "0.2.0"
-last_updated: "2026-02-15"
-web: "https://chrismo.github.io/superkit/_build/tutorials/moar_subqueries/"
----
-
-# Moar Subqueries
-
-## Fork
-
-One hassle to this approach is the limit of 2 forks. Nesting forks works, but
-makes constructing this query a bit more difficult.
-
-## Full Sub-Selects
-   
-As of 20250815 build, this is much, much slower. I'm guessing it's doing a full
-reload of the data file each time.
-
-```
-select
-(select count(*)
-from './moar_subqueries.sup'
-where win is not null) as total_games,
-...
-```
-
-## All Other SQL-Syntax Subqueries
-
-They all take about the same amount of wall-time, but CPU usage is much higher
-due to re-reading the file each time.

package/docs/tutorials/super_db_update.md

@@ -1,31 +0,0 @@
----
-name: super-db-update
-description: "Workarounds for updating data in a SuperDB lake."
-superdb_version: "0.2.0"
-last_updated: "2026-02-15"
-web: "https://chrismo.github.io/superkit/_build/tutorials/super_db_update/"
----
-
-# Updating Data in a Lake
-            
-There are plans to eventually support this, captured in this [GitHub Issue
-#4024](https://github.com/brimdata/super/issues/4024). But for now, we'll have
-to fudge it.
-
-All we can do for now are separate `delete` and `load` actions. It's safer to do
-a load-then-delete, in case the delete fails, we'll at least have duplicated
-data, vs. no data at all in the case of failure during a delete-then-load.
-
-Since we have unstructured data, we can attempt to track the ...
-
-load: {id:4,foo:1,ts:time('2025-02-18T01:00:00')}
-load: {id:4,foo:2,ts:time('2025-02-18T02:00:00')}
-delete: -where 'id==4 and ts < 2025-02-18T02:00:00'
-
-if it's typed data
-
-delete: -where 'is(<foo>) ...'
-
-if we need to double-check duplicate data:
-
-'count() by is(<foo>)'