Choosing a Liquibase Changelog Format: Abstraction vs. Native SQL
Deciding between XML, YAML, and SQL in Liquibase impacts your database portability and validation. This guide compares abstraction vs. native SQL for schema migrations.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Deciding between XML, YAML, and SQL in Liquibase impacts your database portability and validation. This guide compares abstraction vs. native SQL for schema migrations.
Learn how to write safe, reusable SQL with named placeholders like :emp_id in DataGrip, set values via the Parameters dialog, and verify that a PreparedStatement is used.
Learn how ClickHouse’s Distributed table engine can eliminate read bottlenecks in reporting dashboards. Step‑by‑step setup, a real query example, trade‑offs, and practical next steps to scale your cluster without rewriting code.
Knex's handler-style transactions auto-commit on success and auto-rollback on throw, eliminating the leaked-connection failure mode of manual transactions. Here's why they should be your default, plus the trx-forgetting trap to avoid.
DBeaver's Export Data wizard turns any table or query result into a CSV. Here's the configuration that round-trips cleanly, how to verify it, and where the client-side export breaks down.
Build safe, dynamic SQL filters in Knex.js using conditional .where() calls and parameterized values. Avoid string concatenation and SQL injection.
The racket/sql transaction form begins a DB transaction, runs a thunk, and rolls back on any exception, but it does not intercept DDL statements that trigger an implicit commit in the underlying database. When a statement such as ALTER TABLE is executed inside the thunk, many engines (e.g., PostgreSQL, SQLite, MySQL) commit the transaction before the rollbac
Data Processing Trade-offs When managing high-cardinality time-series data in Grafana (v10+), there is an architectural choice between performing complex calculations directly via SQL queries or using the built-in Transformations tab to process result sets after the query returns. Executing logic via SQL pushes the computational load to the database engine,
The documentation doesn't have examples. https://www.postgresql.org/docs/10/datatype-numeric.html#DATATYPE-NUMERIC-TABLE NUMERIC(precision, scale) I want to use the smallest amount of space to save a positive number that will be at most 100 and I need to accept decimal increments of 0.5 What precision and scale should I use in this case?
Asked · 19 Mar 2025, 17:46 UTC
answered · 22 Mar 2025, 17:46 UTC