treeedb currently generates two big tables: node and field. We should explore:
- Generating "narrow" instead of "wide" tables, e.g.,
node_kind, node_start_byte, etc. instead of just node.
- Splitting the tables based on the node kind - the generated Datalog code does this already, so it might be more efficient to do it up front.
treeedbcurrently generates two big tables:nodeandfield. We should explore:node_kind,node_start_byte, etc. instead of justnode.