Yes. A Lightroom catalog file is, after all, just a SQLite database. (Srsly, make a copy of your catalog file, rename it whatever.sqlite and use your favorite SQLite GUI to rip it open and look at the tables and fields). It's just storing the pathame to the RAW file for that file's record in the database. Source: about 1 year ago

I use visidata with a playback script I recorded to open the sheet to a specific Excel tab, add a column, save the sheet as a csv file. Then I have a sqlite script that takes the csv file and puts it in a database, partitioned by monthYear. Source: about 1 year ago

Use the most-used database in the world: https://sqlite.org/index.html. Source: over 1 year ago

With this in mind, I wrote a few versions of this post, but I hated them all. Then I realized that jodliterate PDF documents mostly do what I want. So, instead of rewriting MirrorXref.pdf, I will make a few comments about jodliterate group documents in general. If you're interested in using SQLite with J, download the self-contained GitHub files MirrorXref.ijs and MirrorXref.pdf and have a look. - Source: dev.to / almost 2 years ago

SQLite, by many estimates, is the most widely deployed SQL database system on Earth. It's everywhere. It's in your phone, your laptop, your cameras, your car, your cloud, and your breakfast cereal. SQLite's global triumph is a gratifying testament to the virtues of technical excellence and the philosophy of "less is more.". - Source: dev.to / almost 2 years ago

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