explain-lpts-ddl

Documents LPTS DuckDB extension DDL syntax, including pragmas, table functions, dialects, and known limitations.

8|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/cwida/lpts --skill explain-lpts-ddl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain-lpts-ddl
Source: https://github.com/cwida/lpts/tree/main/.claude/skills/explain-lpts-ddl
Command: npx skills add https://github.com/cwida/lpts --skill explain-lpts-ddl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of needing to manually search source code or external resources to correctly use the LPTS DuckDB extension's features for SQL transpilation, logical plan inspection, and query validation.

Core Features & Use Cases

  • Complete DDL Reference: Covers all LPTS pragmas (PRAGMA lpts, lpts_exec, lpts_check, print_ast), table functions (lpts_query), and dialect configuration settings.
  • Cross-System SQL Transpilation Support: Includes documentation for converting DuckDB queries to PostgreSQL, Spark SQL, BigQuery, and other supported dialects.
  • Use Case: A data engineer can use this skill to quickly look up the correct syntax for PRAGMA lpts_check to validate that transpiled SQL returns identical results to the original query, or use print_ast to debug logical plan conversion issues.

Quick Start

Use the explain-lpts-ddl skill to look up the correct syntax for PRAGMA lpts_check and verify that your transpiled SQL produces the same results as the original query.

Frequently Asked Questions about explain-lpts-ddl

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

FAQPage Schema
How do I inspect the logical plan of a DuckDB query for debugging?

DuckDB SQL transpilation to PostgreSQL, Spark SQL, and BigQuery dialects is supported through the LPTS extension. The explain-lpts-ddl reference documents the dialect configuration options and syntax needed to execute cross-system query conversions.

How do I validate query correctness when converting SQL dialects in DuckDB?

To validate query correctness during SQL dialect conversion in DuckDB, use PRAGMA lpts_check. This verifies that transpiled SQL returns identical results to the original query, with exact syntax detailed in the LPTS DDL reference.

What are the known limitations of the LPTS DuckDB extension for SQL transpilation?

The LPTS DuckDB extension for SQL transpilation has documented known limitations regarding supported query patterns. The explain-lpts-ddl reference outlines these constraints alongside all registered pragmas and table functions to guide valid usage.

Does the LPTS extension support CTE generation and AST debugging for DuckDB queries?

The LPTS extension supports CTE generation and AST debugging for DuckDB queries through its registered pragmas and table functions. The DDL reference covers all supported query patterns and the correct syntax for these features.