How to use the SQL Formatter.
Formatting should preserve tokens and meaning. Use the correct dialect and avoid rewriting literals, comments or identifiers while adjusting layout.
Make the workflow fit your task.
Parse or format the supplied SQL for its actual dialect, changing layout while preserving identifiers, literals and comments. Compare tokens or behavior where needed so formatting does not become an unrequested rewrite.
- What you provide
- SQL text and dialect.
- What you get
- Consistently formatted query without semantic changes.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
select id,name from customers where active=true order by name;
Completed example
SELECT id, name FROM customers WHERE active = true ORDER BY name;
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a formatter rename columns or simplify expressions?
Keep semantic changes separate unless requested. Formatting should improve readability without changing the query's meaning.
Why did a formatted query behave differently?
Inspect altered quoting, comments or dialect-sensitive syntax. Compare the original and revised tokens before blaming whitespace.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑