> What are your thoughts on supporting recursive and, more generally, graph queries?
Yes we want to start tackling recursive queries since there are several ansi sql constructs where that is useful.
> I guess in a broader sense, I'm curious about your thoughts about making Teiid friendly toward querying the entire VDB as a graph.
We are mixed on the approach here. We do have an existing hierarchical model type called an xml document model (use Desinger and import an XSD as a document model). It provides a way to bind the document structure to a set of sql queries, typically at each child iteration. From there the xml document model query language (a restricted sql) has a couple of predicates and other tricks to control searching, projection, etc. of the output document - see XML SELECT Command - Teiid 8.8 (draft) - Project Documentation Editor
So the question always is, do we evolve/refine this approach (in tandem with design time support) or should we start afresh with graph/object db virtualization. Neither seems to gain a lot of traction - and starting afresh has a lot of overlap with the Modeshape project.
> Anyway, this is kind of a long-winded way to realizing that SQL is probably the wrong language and, perhaps, a better approach is to layer a new language/execution-engine onto SQL similar to how OData support was handled.
Yes, both OData and the XML document model logic sit above the normal query engine as they seem best handled outside of the core logic. At of all the possibilities to broaden object/graph support, I'd expect us to keep the focus on OData as its interest seems high.
Thanks for the peek into your thinking.