Liquibase VS Jet Admin

As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago

I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago

I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago

Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago

I don't want to go the expense and setup of a managed database service. I like the concept of using sqlite3, litestream, and AWS S3 for an Internal App. I found an Internal Tools vendor Jetadmin (jetadmin.io) that lists Sqlite as a supported database. It may be that Sqlite is easily integrated with the other tools I looked at, but they don't state it. Source: over 1 year ago

Jetadmin.io - Firestore integration is not working well. Source: almost 3 years ago

Had a look at the github and subsequently the demo, I end up at jetadmin.io which by the looks of it is an interesting low-code/no-code environment. However if you use django-jet doesn't that mean you need a jetadmin account? Source: about 3 years ago