Right, but conceptually the way you interact with it is the same. I'm not trying to belittle what you've done. I'm in fact very excited about it.

And EdgeDB is very needed because it's just an Apple library currently.

Conceptually, my impression is that EdgeDb is relational tables (highly-typed) queried, combined, and modeled as nodes in a graph/tree. Is that conceptually correct?

I don't, but I would like to if I could deploy Swift code to Azure. I love Swift as a language.