ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
The goal is to guarantee that a schema‑change migration can be rolled back completely when it fails, preserving database consistency in a NestJS application that relies on TypeORM for data access. By default TypeORM’s Migration interface runs SQL statements outside any NestJS‑managed transaction, so developers must manually start, commit, or roll back a Quer
Mithril Cache Coherence The goal is to confirm the precise timing of asynchronous cache updates following a successful database commit. Constraints and Uncertainty The system's cache invalidation strategy is dependent on defined transaction boundaries, but the exact timing of asynchronous updates post-commit remains an operational uncertainty. Does the commi
The goal is to allow a Liquibase update operation to be halted after a user‑defined duration, ensuring that any partially applied changeset can be rolled back or left in a known state. Currently Liquibase executes each changeset within a database transaction when supported, but it does not expose a timeout property for the whole update; users must rely on JD
Goal The objective is to guarantee that a schema migration either completes fully or leaves the database unchanged, even when a migration script throws an exception partway through. Current Constraints Expo’s expo-sqlite exposes the native SQLite API. It does not automatically wrap migration blocks in BEGIN / COMMIT / ROLLBACK transactions. When a migration
When using pytest‑rerunfailures to re‑run flaky tests, the plugin currently executes the whole test function, including all fixture setup and teardown, on each retry attempt. The goal is to decide whether a retry should preserve fixture state (i.e., re‑run only the test body) or always re‑create fixtures, especially when fixtures perform external writes such
The goal is to determine whether changes made in an APL workspace can be safely rolled back after a data‑definition language (DDL) statement is issued through the ⎕SQL system function. This requires knowing if the workspace transaction remains open when the underlying DBMS processes the DDL. Uncertainty arises because most relational databases issue an impli
Doctrine Migrations allOrNothing on MySQL: Implicit Commit Limitation When a Doctrine Migration runs on MySQL or MariaDB, the framework wraps the entire migration version in a transaction if allOrNothing=true . However, MySQL treats many DDL statements (CREATE, ALTER, DROP) as implicit commits, breaking the transactional guarantee. The migration remains mark
expo
pytest
apl
doctrine
nestjs