MysqlDdlImplicitlyCommitsTransaction

warning native on by default

Group: Probable bugs

Some MySQL DDL statements implicitly commit an active transaction. Keep them outside operations that depend on rolling back the transaction.

Example

<?php
$p=new PDO("mysql:host=localhost");$p->beginTransaction();$p->exec("CREATE TABLE t (id INT)");$p->rollBack();

Reported:

• line 2: Keep implicitly committing DDL outside rollback-dependent transactions.

Detection

• A PDO connection has a literal mysql: DSN, beginTransaction precedes exec of literal CREATE TABLE, ALTER TABLE or DROP TABLE (not TEMPORARY), then rollBack. No commit or unknown connection escape intervenes. Highlight DDL operation.
• Resolve builtin functions, classes, constants and methods; user-defined lookalikes are excluded. Follow only bounded local proof in one lexical scope.
• Emit one finding per violating operation, not per supporting evidence statement. When the proof is inconclusive, nothing is reported.

Exceptions (no report)

• Do not report unresolved or shadowed builtin names, unknown values, or incomplete receiver/type provenance. Unknown calls, aliases escaping, and intervening writes invalidate local proof. Similar code outside the stated detection contract is not a finding.
• Both standard suppression forms suppress this native ID.

Fix

None. Choosing a repair requires intent or additional runtime information.

PHP versions

Available throughout supported PHP 5.3–8.5 where the referenced builtin/extension is available. Respect syntax/version-specific receiver contracts; unavailable APIs are not this rule’s concern.

Configure

In custos.json:

{
  "rules": {
    "MysqlDdlImplicitlyCommitsTransaction": {
      "enabled": false
    }
  }
}

Suppress

Before the statement or declaration (or the first statement of the file):

// @custos-ignore MysqlDdlImplicitlyCommitsTransaction