Description
Format separately quoted qualified SQL identifier components; literal dots inside components remain data, not qualification, and no schema lookup is performed.
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.
Format separately quoted qualified SQL identifier components; literal dots inside components remain data, not qualification, and no schema lookup is performed.
When to use this tool
Use this tool to format separately quoted qualified SQL identifier components; literal dots inside components remain data, not qualification, and no schema lookup is performed.
How to use the tool and how it works
- Enter parts, style using the field definitions below.
- Run the operation. Correct input errors before interpreting an output.
- Read result.identifier. Use the ordering, boundary rules and absence conditions described below.
Require nonempty identifier parts and a supported quote style. Quote each part independently, then join them with periods.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| parts | Nonempty qualified-name parts, quoted independently before joining. | Dense list of at most 128 strings, each at most 8,192 UTF-16 code units. |
| style | Exact identifier quote style: double, backtick or bracket. | Text, at most 8,192 UTF-16 code units; the operation’s grammar also applies. |
| Output field | Interpretation |
|---|---|
| result | Object containing the named fields below. |
| result.identifier | Quoted qualified name with parts joined by periods. |
{
"input": {
"parts": [
"a",
"b.c"
],
"style": "double"
},
"output": {
"result": {
"identifier": "\"a\".\"b.c\""
}
}
}Limitations and assumptions
- A period inside one part remains part of that quoted identifier rather than splitting a qualified name.
- 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 Backtick Identifier Formatter
Restricted SQL backtick quote formatter using doubled closing quotes only; NUL rejects, no backslash mode, database execution or SQL-injection safety guarantee.
- SQL Bracket Identifier Formatter
Restricted SQL bracket quote formatter using doubled closing quotes only; NUL rejects, no backslash mode, database execution or SQL-injection safety guarantee.