Postgres.js VS Liquibase

I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon: https://github.com/neondatabase/neon/issues/4989. Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database. To the PMs of Neon, put yourself in the shoes of a new... - Source: Hacker News / 18 days ago

I'd push you to consider using postgres, slonik or similar for database queries. With these libraries, you just write SQL, but they perform input sanitization for you. So you can safely write:. Source: 5 months ago

There's also https://kysely.dev/ but personally I handwrite my queries with https://github.com/porsager/postgres for flexibility and performance most orms use node-pg lib which has shit performance. - Source: Hacker News / 7 months ago

When viewed as a DSL for set theory, views, CTEs, set-returning functions, et al are indeed proper first-class query abstractions. When viewed through the lens of general purpose imperative or functional programming languages, it's easy to see how it can be seen as falling short. I'll admit much of the tooling and driver APIs leave a lot to be desired. Some tools do make good efforts though such as nested... - Source: Hacker News / 8 months ago

Demonstrate how easily and accidentally one can make an SQL injection with these: https://github.com/porsager/postgres. - Source: Hacker News / 10 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