Building SaarDB, Part 6: How SQL Queries Become Key-Value Operations
go
dev.to
In Blog 5, we built a SQL parser. It can take this: INSERT INTO payments VALUES (500, payment_1, pending, 1) and turn it into a struct: InsertIntoTable{ TableName: "payments", ColumnValues: []string{"500", "payment_1", "pending", "1"}, } But this is still not enough for the storage engine. Our storage engine only knows how to store key-value pairs. It does not know what a table is. It does not know what a column is. It does not know that 500 is an integer, pending is a