graphjin VS atlas

This one looks interesting if you like GraphQL… https://graphjin.com

You're right. Django made a ton of tables, and it's pretty insightful to think about all the stuff it's trying to consider and a nightmare to migrate that framework. Django might have simplified some stuff, but it's still too opaque for my taste and the overall end goals of the project. Currently, I'm testing using graphjin (it doesn't have the best documentation, but it does boast an SQL generation capability that I philosophically think is the best way to do things).

Checkout GraphJin it's an automatic GraphQL to SQL compiler, you write your database queries in GraphQL instead of SQL and it compiles them into efficient SQL on the fly. Works as a library in GO and NodeJS. https://github.com/dosco/graphjin

In GraphJin an automatic GraphQL to SQL compiler we use the gnomock library it startups a database instance (docker) then create the schema and tests data and finally our code connects to it and runs a series of tests. We run these across Mysql, Postgres and a few other DB's. Gnomock supports a wide range of them. Right now we don't take down the db for every test only between test runs but its fast enough that we could. This whole thing runs of a simple `go test -v .` command and we run it on every commit using a githook. https://github.com/dosco/graphjin/blob/master/tests/dbint_te...

This was a bug in GraphJin it has since been fixed. The issue was that you were trying to have multiple subscriptions over a single websocket this did not work (it should) and now it does. https://github.com/dosco/graphjin/commit/43e619b2ff392dd42b99a4d56074a041a54b0e1c

Not exactly GraphQL is just a format to define what data you want back from someplace. You can use it in a browser app to request data from a backend GraphQL server or you can use it as an ORM within your backend app to fetch data from a database using a library like GraphJin. https://github.com/dosco/graphjin

Check out: https://github.com/ariga/atlas

(I'm one of the authors of this project).

fwiw, I personally am interested in this approach too[0]. I keep running into roadblocks around the ordering of events and some of the hairy issues around "destructive" actions (eg: renaming columns). i think we can get there, especially once we make progress with this LSP.

There are other notable mentions in this space:

Reshape: https://fabianlindfors.se/blog/schema-migrations-in-postgres...

Atlas: https://atlasgo.io/

[0] https://github.com/kiwicopple/declarative-schemas

Atlas: https://github.com/ariga/atlas. It can be integrated with any ORM, but also has an official one for GORM: https://atlasgo.io/guides/orms/gorm

Run the queryx db:create command to create a PostgreSQL database, and then run queryx db:migrate to automatically create the database migration files and database structure. Queryx’s database schema management is built upon Atlas.

One of https://atlasgo.io's creators here.

In this case, I'd recommend you to check Atlas: https://github.com/ariga/atlas

My name is Rotem, I'm one of the creators of Atlas (https://atlasgo.io) a modern open-source schema management tool. Recently one of our engineers created a cool Django plugin that creates beautiful (in my eyes at least ;-)) and shareable ERDs from your Django data models.

Yes, there is: Atlas! https://atlasgo.io / https://github.com/ariga/atlas.

Hi there You should take a look at Atlas - https://atlasgo.io which can help your team in many aspects of CI/ CD for databases : * CI - detect (and prevent) risky / incorrect migrations automatically * CD - support for modern deployment infrastructure (terraform, helm, etc)

You might want to check out Atlas. It provides automatic migration planning for GORM, and has various guides on how deploying schema migration on the popular platform and tools, such as Helm, Kubernetes and ECS.