dolt

We built a MySQL-compatible one and are building a Postgres-compatible one :-) Free and open source. https://github.com/dolthub/dolt We use the reset functionality to speed up our tests. https://www.dolthub.com/blog/2022-06-10-enginetest-perf/

The readme mentions at least one interesting use which presumably is the impetus for its creation: https://github.com/dolthub/dolt

Hi, this is my project :) For us this package is most important as the query engine that powers Dolt: https://github.com/dolthub/dolt We aren't the original authors but have contributed the vast majority of its code at this point. Here's the origin story if you're interested: https://www.dolthub.com/blog/2020-05-04-adopting-go-mysql-se...

Not a proxy in the traditional sense, no. go-mysql-server is a set of libraries that implement a SQL query engine and server in the abstract. When provided with a compatible database implementation using the provided interfaces, it becomes a MySQL compatible database server. Dolt [1] is the most complete implementation, but the in-memory database implementation the package ships with is suitable for testing. We didn't extract go-mysql-server from Dolt. We found it sitting around as abandonware, adopted it, and used it to build Dolt's SQL engine on top of the existing storage engine and command line [2]. We decided to keep it a separate package, and implementation agnostic, in the hopes of getting contributions from other people building their own database implementations on top of it. [1] https://github.com/dolthub/dolt [2] https://www.do

Yes, triggers and stored procedures are supported. Concurrency is the only real limitation in terms of functionality. The bundled in-memory database implementation is mostly for use in testing, for people who run against mysql in prod and want a fast compatible go library to test against. For a production-ready database that uses this engine, see Dolt: https://github.com/dolthub/dolt

It's a pretty good default stance, yeah. We have been trying to convince people to use our new database [1] for several years and it's an uphill battle, because Postgres really is the best choice for most people. They really have to need our unique feature (version control) to even consider it over Postgres, and I don't blame them. [1] https://github.com/dolthub/dolt

Somebody already said this, but we built exactly this and it's called Dolt. https://github.com/dolthub/dolt Would love to hear how it addresses your use case or falls short.

Have you considered https://github.com/dolthub/dolt for your use case?

Maybe this https://github.com/dolthub/dolt

We implemented a query optimizer with a flexible intermediate representation in pure Go: https://github.com/dolthub/go-mysql-server Getting the IR correct so that it's both easy to use and flexible enough to be useful is a really interesting design challenge. Our primary abstraction in the query plan is called a Node, and is way more general than the IR type described in the article from OP. This has probably hurt us: we only recently separated the responsibility to fetch rows into its own part of the runtime, out of the IR -- originally row fetching was coupled to the Node type directly. This is also the query engine that Dolt uses: https://github.com/dolthub/dolt But it has a plug-in architecture, so you can use the engine on any data source that implements a handful of Go interface.