Fix ON DELETE SET NULL formatting

[VrtxOmega]

Fixes #132.

Summary

• Treat SET NULL as a regular reserved phrase so foreign-key actions like ON DELETE SET NULL do not split at SET.
• Add a regression test covering the reported table definition and formatting options.

Validation

• cargo fmt --check
• cargo test
• Manual CLI repro for the issue input now keeps ON DELETE SET NULL on the column definition line.

[kilo-code-bot]

WARNING: SET DEFAULT is still tokenized as a top-level SET clause

This special-cases SET NULL, but referential actions also allow SET DEFAULT. For ON DELETE SET DEFAULT and ON UPDATE SET DEFAULT, the tokenizer will still match the plain SET branch here, classify it as ReservedTopLevel, and split the foreign-key action across lines again.

---

_{Reply with @kilocode-bot fix it to have Kilo Code address this issue.}

[kilo-code-bot]

Code Review Summary

Status: 1 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
src/tokenizer.rs	617	SET NULL is handled, but valid referential actions using SET DEFAULT still fall through to the top-level SET rule and remain mis-formatted.

Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

None.

Files Reviewed (2 files)

• src/tokenizer.rs - 1 issue
• src/lib.rs - 0 issues

Fix these issues in Kilo Cloud

---

_{Reviewed by gpt-5.4-20260305 · 469,562 tokens}