How vovinsa/vovinquity works
Main Components
The system should be represented as a layered architecture with the following main components from top to bottom:
a. Query Interface Layer
• Interactive SQL Console (entry point)
b. Query Processing Layer
• Parser (/src/parser)
• Planner (/src/planner)
• Executor (/src/executor)
c. Storage Layer
• Table Management (/src/storage/table)
• Index Management (/src/storage/index)
• Catalog Management (/src/catalog)
Component Relationships and Data Flow
SQL Query Input
• ↓
Parser (SQL Parsing)
• ↓
Planner (Query Planning)
• ↓
Executor (Query Execution)
• ↓
Storage Layer (Data Access)
Specific Component Details
For each major component, include these important elements:
Parser Component:
• Input: SQL string
• Output: Parse tree
• Files: parser.h/cpp
Planner Component:
• Input: Parse tree
• Output: Query plan nodes (nodes.h)
• Supported operations: CREATE TABLE, INSERT, SELECT, ORDER BY, GROUP BY, WHERE, Aggregates
• Files: planner.h/cpp
Executor Component:
• Input: Query plan
• Output: Query results
• Files: executor.h/cpp, executor_nodes.h
Storage Layer:
• B+ Tree Index implementation (bplus_tree.h/cpp)
• Table management (table.h/cpp)
• System tables (system_table.h/cpp)
• Schema definitions (schema.h)
• Tuple handling (tuple.h)
Important Architectural Patterns to Highlight
• Layered architecture pattern
• Pipeline pattern for query processing
• B+ Tree for indexing
• Separation of concerns between different layers