Writing a SQL database from scratch in Go

Unexpected, but welcome, to see the first part in the series on here right now. I just published the second part [0] today, featuring binary expressions and WHERE filtering. It also updates the REPL to use a prettier table-printing library and a readline implementation.<p>The repo [1] has some additional bare notes on architecture and links to similar, more mature projects (primarily go-mysql-server and ramsql).<p>[0] <a href="https:&#x2F;&#x2F;notes.eatonphil.com&#x2F;database-basics-expressions-and-where.html" rel="nofollow">https:&#x2F;&#x2F;notes.eatonphil.com&#x2F;database-basics-expressions-and-...</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;eatonphil&#x2F;gosql" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;eatonphil&#x2F;gosql</a>

Great blog post!<p>I&#x27;d just like to add for the curious, that usually you&#x27;d use goyacc for parsing SQL.<p>And most serious SQL projects in Go have started with the SQL parser from vitess and adapted it to their use case (which is just funny trivia, but for anything big, I recommend it, did the same for OctoSQL [0]).<p>[0]: <a href="https:&#x2F;&#x2F;github.com&#x2F;cube2222&#x2F;octosql" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;cube2222&#x2F;octosql</a>

Probably the first article Ive ever read about lexical parsing with code that i have actually understood - and I dont even program in golang. Great job.

<i>selectKeyword keyword = &quot;select&quot;</i><p>I don&#x27;t work with Go, so this may be a requirement of the language that I don&#x27;t know, but whenever I see lines like this, it automatically brings up the question <i>why?</i> --- do you really expect to need to rename the SELECT keyword? Especially when it&#x27;s named &quot;selectKeyword&quot;. Why not just use the string constant? Ditto for the others like &quot;leftparenSymbol&quot; --- I see there&#x27;s explicit character constants in some of the other code too... it reminds me of the classic anti-pattern like &quot;int five = 5;&quot;.<p>Also, you may find the full SQL grammars interesting to look through --- they are quite a bit more complex than the subset presented in the article: <a href="https:&#x2F;&#x2F;ronsavage.github.io&#x2F;SQL&#x2F;" rel="nofollow">https:&#x2F;&#x2F;ronsavage.github.io&#x2F;SQL&#x2F;</a>

Curious - would Rust be more appropriate than Go for such a task?

Do you know about a tutorial or a book that helps write Database from scratch either in Java or C?

Are you going to add persistence in an upcoming part?