teaguesterling / duckdb-dataconnector-agent Goto Github PK

Loading the httpfs extension crashes when the __snprintf_chk function cannot be found. Likely a missing library from the Dockerfile.

The package-lock.json file is not up-to-date due to both laziness and issues with the NPM duckdb package.

Running a query such as:

{
   Album {
      Tracks {
         Name 
      }
   }
}

When Album and Track are in different databases results in a SQL exceptions due to the JSON_EACH function not existing in DuckDB.

It would be particularly nice to have some way to "auto-discover" potential relationships (similar to foreign keys) without the performance overhead of using them as column constraints.

One way may be to allow it to be pre-specified as part of the GraphQL config or through a separate file, but that would be clunky.

The SQLITE_SCHEMA table does include views, but only with their defining DDL and not the underlying schema.

It would be particularly helpful to be able be able to use views (such as those created off of external data sources) as part of the GraphQL schema. This would require either "peeking" at the data or, preferably, replacing the use of the SQLITE_SCHEMA with the information_schema tables to get the previously identified schemas of views.