ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Transactional Migrations vs. Disabling Transactions The goal is to deploy schema changes in a small application without downtime. Knex runs migrations inside a transaction by default, ensuring atomicity, but MySQL 5.7+ rejects certain ALTER TABLE statements that cannot be executed transactionally. Setting migrations: { transaction: false } allows those ALTER
Goal Determine the exact transactional boundaries for schema changes in Azure SQL Database, specifically focusing on operations that are auto‑committed and cannot be rolled back, and explore whether any configuration can enforce rollback safety. Current Constraints DDL statements are generally transactional, but some, such as ALTER TABLE DROP COLUMN , are au
When using Bun's built‑in sqlite module, developers often wrap schema migrations in an explicit transaction expecting that a ROLLBACK will undo any CREATE, ALTER, or DROP statements if something goes wrong. However, SQLite issues an implicit commit for DDL statements, which ends the open transaction before the ROLLBACK is processed, leaving the schema change
A design is needed to retry a write goal that can fail transiently while guaranteeing the dynamic fact is present exactly once and external side effects are not duplicated. The constraint is SWI-Prolog database semantics. transaction/1 runs a goal atomically and rolls back assert/retract changes on failure, so a retry loop around transaction/1 cannot leave p
Schema Change Transaction Boundary Problem Doctrine DBAL schema modifications executed through Migration::up() operate outside active transaction boundaries, creating a critical interoperability question with Doctrine ORM's explicit transaction control features introduced in version 2.5+. When DDL operations like ALTER TABLE execute, most database drivers au
In Phalcon 5.x, setting PDO::ATTR_TIMEOUT on a database adapter enforces a statement execution timeout, but the framework does not specify whether an ensuing timeout exception should automatically roll back an active transaction. The PDO driver throws an exception when the query exceeds the timeout, yet the transaction context remains open unless the applica
Goal Determine how SQLite’s foreign key enforcement behaves when a new constraint is added via ALTER TABLE … ADD COLUMN on a database where PRAGMA foreign_keys = ON is active. Constraints & Uncertainty SQLite 3.x – foreign key enforcement is disabled by default and must be enabled per connection. Existing data may already violate the new foreign key cons
Goal Determine whether Knex.js should automatically emulate savepoints for databases that lack native savepoint support when a nested transaction is rolled back, or instead surface the limitation through an explicit error. Constraints and Uncertainty Knex.js currently issues a ROLLBACK TO SAVEPOINT on databases with savepoint capability (e.g., PostgreSQL, SQ
Background When a LuaSQL client executes a DDL statement such as CREATE TABLE inside a transaction, the expectation is that a subsequent connection:rollback() will undo the schema change. In practice, the outcome depends on the underlying driver and database server. Goal Determine whether a DDL executed within a LuaSQL transaction can be safely rolled back a
azuresqldatabase
sqlite
bun
prolog
doctrine
phalcon
knexjs
lua
mysql