SQLPage - Build SQL-only websites VS Liquibase

Saving a few clicks for readers: Project page: https://sql.ophir.dev/. - Source: Hacker News / 2 months ago

I am currently looking for a solution to run automated tests on a sql website generator I am working on ( https://sql.ophir.dev ) I wanted to use hurl (https://hurl.dev/), but Bruno's UI seems to be useful while developing the tests... Has someone tried both ? Which is better for automated testing, including when the response type is html and not json? - Source: Hacker News / 2 months ago

Full fledged BI tools like Superset and Metabase are amazing for their intended use cases. But they may be an overkill if your primary use case is to infrequently build semi-interactive reports for non-technical end-users and your use cases are are mostly covered by standard graphs & tables. Esp. So if you are familiar with SQL and have access to the underlying data source. Two nifty utilities I have found to be... - Source: Hacker News / 3 months ago

I feel obligated to add a shameless plug here. The idea is very close to a project I presented at pgconf.eu last week: SQLPage https://sql.ophir.dev/ SQLPage has the same goal as postgrest+htmx, but is a little bit higher level. It let's you build your application using prepackaged components you can invoke directly from SQL, without having to write any HTML, CSS, or JS. - Source: Hacker News / 5 months ago

I have been thinking about that a lot recently. Where I work, we spend a very small fraction of our time on building things that are unique to our business. Maybe we are doing something very wrong, but I am under the impression that most of the code that gets written is extremely low-entropy. This low-entropy, repetitive coding is not limited to the user interfaces. We do tend to describe the same structures and... - Source: Hacker News / 6 months 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