Testing Index Impact Safely with Oracle Invisible Indexes
Learn how to use Oracle invisible indexes to test the effect of dropping an index without actually removing it, and verify plan changes safely.
Loading…
ReadMeFeed / Community knowledge
#ddl
Real questions. Useful conversations. Find the people who know your stack.
Generating Migration Scripts with DataGrip's Schema Comparison Tool
DataGrip's Compare Structure tool diffs two schemas and generates migration DDL. Learn the workflow, why renames become destructive drop-and-adds, and how to verify the output safely.
datagripConfiguring JDBC Savepoint usage for safe rollback after DDL schema changes
Goal Ensure that a transaction can be rolled back to a known point after executing a schema‑altering statement (e.g., ALTER TABLE) so that any unintended data changes are undone while preserving the ability to commit other work. Constraints / Uncertainty Many relational databases issue an implicit commit when a DDL statement is executed, which may terminate
javaFireDAC Schema Synchronizer: enforcing reverse DDL generation before forward DDL runs
FireDAC's Schema Synchronizer in RAD Studio compares two database structures and generates a forward DDL script that applies the detected differences. The tool can also emit a reverse DDL file that undoes those changes, but that output is optional and must be selected manually for each run. There appears to be no documented option that makes reverse DDL gene
racket/sql: transaction rollback fails with 'a command in the transaction has already caused a commit' after ALTER TABLE
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
racketDBIx::Class::Migration::Version rollback safety for non-transactional DDL
DBIx::Class::Migration::Version provides a structured way to manage schema evolution using up and down methods. While this framework tracks versioning via a metadata table, the actual execution of Data Definition Language (DDL) statements depends on the underlying database engine's capabilities. In environments using databases that do not support transaction
perlFireDAC + PostgreSQL: Is DDL Rollback Guaranteed in Transactions?
FireDAC + PostgreSQL: DDL Rollback The goal is to determine whether schema‑changing statements executed through FireDAC’s TConnection and TTransaction components can be safely rolled back when targeted at PostgreSQL. The primary constraint is that FireDAC does not automatically wrap DDL in a transaction; developers must explicitly begin a transaction, execut
radstudioLuaSQL transaction limits regarding DDL schema changes
When managing database migrations via LuaSQL, there is a discrepancy in how Data Definition Language (DDL) statements interact with transaction boundaries compared to Data Manipulation Language (DML) statements. In many database drivers, executing a schema change—such as CREATE TABLE or ALTER TABLE —triggers an implicit commit. This behavior potentially bypa
luaDoes Knex.js provide a mechanism to handle partial DDL failures in non-transactional dialects?
Migration State and DDL Rollbacks Knex.js manages migration state via a migrations table and a lock mechanism to prevent concurrent execution. For dialects supporting transactional DDL, such as PostgreSQL, Knex wraps migrations in transactions to ensure atomicity. However, MySQL and MariaDB do not support rolling back DDL statements. Consistency Constraints
knexjs
mysql