prisma-engines

If you wish to auto-generate migrations, there are declarative schema change tools available for most relational databases. I'm the creator of Skeema [1] which provides them for MySQL, but there are options for other DBs too [2][3][4]. Prisma's migration system actually partially copied Skeema's design, while giving credit in a rather odd fashion which really rubbed me the wrong way. From Prisma Migrate's architecture doc: "The workflow of working with temporary databases and introspecting it to determine differences between schemas seems to be pretty common, this is for example what skeema does." [5] While I doubt I was the first person to ever use that technique, I absolutely didn't copy it from anywhere, and I'm not aware of any other older schema change systems that work this way. It was certainly never "pretty common" prior to Skeema

We solved this with flat vectors and just sharing index values in cheap walker objects. It is much nicer to work with compared to arc/weak pointers. Code here: https://github.com/prisma/prisma-engines/tree/main/libs%2Fda...

Because Prisma Python currently interfaces with the Rust engine over HTTP (I am looking into changing this) and the Rust engines can be found here: https://github.com/prisma/prisma-engines

Thanks! I know of a couple Postgres tools that work in a declarative fashion: migra [1] and sqldef [2]. Migra is Postgres-specific. Its model is similar to Skeema's, in that the desired-state CREATEs are run in a temporary location and then introspected, to build an in-memory understanding of the desired state which can be diff'ed against the current actual state. (This approach has also been borrowed by other recent tools, including Prisma Migrate [3]). In this manner, the tool doesn't need a SQL parser, instead relying on the real DBMS to guarantee the CREATE is interpreted correctly with your exact DBMS version/flavor/settings. In contrast, sqldef supports multiple databases, including Postgres and MySQL (among others). Unlike other tools, it uses a SQL parser-based approach to build its in-memory understanding of the desired state. As

I think it has a high chance of happening. Most of the bigger frameworks and libraries have moved to typescript and with remaining on typings or ts rewrite. Deno will probably take over. A new interesting phenomenon I noticed is few bigger frameworks now have their core written in rust with language agnostic interface on top. example: - https://github.com/prisma/prisma2 - https://github.com/prisma/prisma-engine We have yew, snow, draco and seed along with some shot at cross-platform native frameworks. The progress is pretty fast. Not to mention wasmer is pretty sweet - https://github.com/wasmerio/wasmer

The Rust code is here: https://github.com/prisma/prisma-engine/ And the old Scala codebase here: https://github.com/prisma/prisma/ The old codebase has parts in Rust, so counting the lines is not that straightforward.

The same day as async/await hits stable, the next Prisma alpha is released and is the first alpha that's based on Futures and async/await. https://github.com/prisma/prisma-engine/ Been working with the ecosystem since the first version of futures some years ago, and I must say how things are right now it's definitely much much easier. There are still optimizations to be made, but IO starts to be in a good shape!