Description
Audit repeated explicit positive numbered placeholder occurrences and indexes; repeats are legal binding reuse, not automatically errors.
SQL identifiers, string literals and parameter placeholders serve different roles. Quote doubling can encode a single token in a selected dialect, while binding indexes connect placeholders to supplied values. These tools work with explicit tokens or lists; they do not connect to a database or parse an entire SQL program.
Audit repeated explicit positive numbered placeholder occurrences and indexes; repeats are legal binding reuse, not automatically errors.
When to use this tool
Use this tool to audit repeated explicit positive numbered placeholder occurrences and indexes; repeats are legal binding reuse, not automatically errors.
How to use the tool and how it works
- Enter indexes using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.repeated. Use the ordering, boundary rules and absence conditions described below.
Group equal positive placeholder indexes and return only repeated groups with their original occurrence positions.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| indexes | One-based placeholder indexes; positions of list entries remain zero-based. | Dense list of at most 128 finite numbers; integer/shape constraints above also apply. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.repeated | Repeated placeholder indexes/names with original occurrence positions. |
{
"input": {
"indexes": [
1,
3,
3
]
},
"output": {
"result": {
"repeated": [
{
"key": "3",
"indexes": [
1,
2
]
}
]
}
}
}Limitations and assumptions
- Group keys are decimal strings; absence from this report does not mean bindings are complete.
- Placeholder indexes are one-based when stated; occurrence positions and binding-list positions are zero-based. Supported quote styles are explicit local conventions rather than a promise of compatibility with every database dialect.
- Every declared top-level input field is required and unexpected fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and no larger in absolute magnitude than the safe-integer limit; operations returning exact large integers use decimal text. Positions are zero-based and spans end exclusively unless the operation explicitly states a different convention.
Alternative or Complementary methods
Use the database driver’s parameter binding for values and the target dialect’s identifier rules for names. Token formatting and occurrence audits are separate from execution, authorization and complete query validation.
References
Similar or alternative tools
- SQL Numbered Placeholder Formatter
Format a positive PostgreSQL-style numbered SQL placeholder token; no binding, query parsing or database access.
- SQL Numbered Placeholder Gap Audit
Audit gaps in explicit numbered SQL placeholder occurrences from one through the observed maximum; bounded to 128, no SQL lexer or parameter-count assumption.