MysqliInvalidBindingType

warning native on by default

Group: Probable bugs

mysqli bindings accept only the supported integer, floating-point, string and blob type letters. Correct unsupported characters in the type string.

Example

<?php
function bad(mysqli_stmt $s){$s->bind_param("x",$v);}

Reported:

• line 2: Use only supported mysqli binding type letters.

Detection

• Resolved mysqli_stmt::bind_param literal type string contains a character other than i,d,s,b. Highlight the type-string argument.
• 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": {
    "MysqliInvalidBindingType": {
      "enabled": false
    }
  }
}

Suppress

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

// @custos-ignore MysqliInvalidBindingType