How shreyasmahajann/sql_in_cpp works
Project type and purpose
• This is a standalone, file-based Database Management System written in C++ (a monolithic backend application).
• It provides basic database and table operations, stores data in CSV files, and is invoked via a simple CLI entry point (main.cpp).
File structure
• Top-level C++ sources:
• main.cpp – application entry and initialization logic
• database.cpp / database.h – Database class handles DB creation, loading, and registry (information_schema.csv)
• table.cpp / table.h – Table class (inherits/uses Database) handles column definition (columns.csv), data insertion (data.csv), and display
• Build: Makefile for compilation and clean
• Storage directory: Databases/
• information_schema.csv – global registry of databases
• Per–database folders (e.g., baseDb/, db1/), each containing tables.csv plus subfolders per table
• Each table subfolder holds columns.csv and data.csv
README for additional insights
• Describes system initialization (initializeDatabaseSystem()), supported data types, core classes, file-storage layout, and example usage.
• No external services or networking—pure filesystem I/O and in-memory class logic.
• CLI / Application Layer (main.cpp)
• Initialization Module (initializeDatabaseSystem())
• Database Manager (Database class)
• Table Manager (Table class)
• File System Storage (folder structure & CSV files)
• Registry Files:
– information_schema.csv (global DB registry)
– tables.csv (per-DB table registry)
– columns.csv & data.csv (per-table metadata & data)
1. CLI invokes Initialization Module → creates Databases/ + information_schema.csv
2. User calls Database constructor → Database Manager reads/writes information_schema.csv, creates DB folder, writes tables.csv
3. User calls Table constructor → Table Manager calls Database Manager to verify DB, updates tables.csv, creates table folder, writes columns.csv
4. Table Manager.addRow() → writes to data.csv
5. Table Manager.displayTable() → reads columns.csv & data.csv → outputs to console
c. Architectural patterns & design principles:
• Monolithic layered architecture (CLI → Business logic classes → Persistence)
• Single Responsibility (Database vs. Table)
• File-based persistence abstraction behind the Database/Table API
d. Key technologies and libraries:
• C++11 filesystem & I/O (<filesystem>, <fstream>, <iostream>)
• Makefile for build orchestration
• CSV format for persistence