Official migration tooling

[IngwiePhoenix]

I am using the rust-based surrealdb-migrations but I keep running into more and more issues - and with there not being any ORM adapter for SurrealDB (I use Go, React and ES6) it is kinda hard to do database-in-git properly...

So, I wanted to put this idea out here for an official migration tool.

Use-case:

1. You create a project. Yay!
2. You define an initial schema for stuff and drop that in to a temporary local instance.
3. But, one of the fields was the wrong type - you ment to do array<record<something>> instead of just record<something...
4. So you create a new migration that does that; it removes the old field and instead adds the new field in it's place.
5. That migration is but a tiny script, but you can check it into Git - which means, it is inherently documented by at least it's commit message.
6. Someone else pulls your project and boots it, the migrations get applied as part of your entrypoint (i.e. a Docker ENTRYPOINT or CMD)
7. You notice a bug in your project and roll back a migration.
8. Your user can roll it back too to resolve an issue.

Just wanted to put this out here.

For context: I've spent ~4 months building a project for my work with Go, SurrealDB, React and schadcn-ui...and one of the biggest bottlenecks was either React or SurrealDB itself, and often not because of the language, but the tooling around it. The Go client is a mess and not like the other DB's clients - so, no existing tooling can be used there...

But migrations would go a long way.

Pseudo-examples:

$ surreal migration create
$ surreal migration status
$ surreal migration apply
$ surreal migration down 1