df-dev

Implement upstream dialect contributions in the DataFusion SQLParser.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/guan404ming/gmccc --skill df-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: df-dev
Source: https://github.com/guan404ming/gmccc/tree/main/skills/datafusion/df-dev
Command: npx skills add https://github.com/guan404ming/gmccc --skill df-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DataFusion's SQLParser often needs support for additional SQL dialects; this skill streamlines implementing upstream dialect contributions to extend compatibility and correctness.

Core Features & Use Cases

  • Add or modify dialect features in the parser by reusing existing infrastructure (e.g., parse_begin_exception_end()) and updating src/.
  • Increase test coverage by adding dialect-specific tests in tests/sqlparser_<dialect>.rs.
  • Documentation alignment by including official dialect references in code comments and PR notes.

Quick Start

Implement the next upstream dialect contribution in the DataFusion SQLParser.

Frequently Asked Questions about df-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new SQL dialect to the DataFusion SQLParser?

To add a new SQL dialect to the DataFusion SQLParser, you modify the relevant src files to implement parsing logic, add dialect-specific tests in tests/sqlparser_<dialect>.rs, and include official documentation references in your code comments.

How should I validate Rust parser changes before submitting a DataFusion upstream contribution?

Validate Rust parser changes for upstream DataFusion contributions by running cargo test to ensure correctness, cargo clippy for linting, and cargo fmt for formatting. You must also update target/NOTE.md and ensure your PR title includes the dialect name.

Can I reuse existing parsing infrastructure when extending DataFusion SQLParser dialects?

Yes, you can reuse existing parsing infrastructure when extending DataFusion SQLParser dialects. The skill leverages existing functions like parse_begin_exception_end() to implement upstream dialect contributions and extend supported syntax efficiently.

What is the process for testing upstream dialect contributions in SQLParser?

Testing upstream dialect contributions in SQLParser involves adding specific test cases to the tests/sqlparser_<dialect>.rs file. This increases test coverage and ensures the newly added or modified parsing logic correctly handles the targeted dialect scenarios.

Why does my DataFusion SQLParser PR need official documentation references?

Your DataFusion SQLParser PR needs official documentation references to maintain documentation alignment. Including these references in code comments and PR notes ensures the implemented dialect features follow official syntax specifications and remain verifiable.