Struct DuckDBDialect

pub struct DuckDBDialect { /* private fields */ }

Implementations

impl DuckDBDialect

pub fn new() -> DuckDBDialect

Trait Implementations

impl Default for DuckDBDialect

fn default() -> DuckDBDialect

Returns the “default value” for a type.

impl Dialect for DuckDBDialect

fn identifier_quote_style(&self, _: &str) -> Option<char>

Return the character used to quote identifiers.

fn character_length_style(&self) -> CharacterLengthStyle

The character length extraction style to use: CharacterLengthStyle

fn division_operator(&self) -> BinaryOperator

The division operator for the dialect Most dialect uses BinaryOperator::Divide (/) But DuckDB dialect uses BinaryOperator::DuckIntegerDivide (//)

fn with_custom_scalar_overrides( self, handlers: Vec<(&str, Box<dyn Fn(&Unparser<'_>, &[Expr]) -> Result<Option<Expr>, DataFusionError> + Sync + Send>)>, ) -> DuckDBDialect

Extends the dialect’s default rules for unparsing scalar functions. This is useful for supporting application-specific UDFs or custom engine extensions.

fn scalar_function_to_sql_overrides( &self, unparser: &Unparser<'_>, func_name: &str, args: &[Expr], ) -> Result<Option<Expr>, DataFusionError>

Allows the dialect to override scalar function unparsing if the dialect has specific rules. Returns None if the default unparsing should be used, or Some(ast::Expr) if there is a custom implementation for the function.

fn supports_nulls_first_in_sort(&self) -> bool

Does the dialect support specifying NULLS FIRST/LAST in ORDER BY clauses?

fn use_timestamp_for_date64(&self) -> bool

Does the dialect use TIMESTAMP to represent Date64 rather than DATETIME? E.g. Trino, Athena and Dremio does not have DATETIME data type

fn interval_style(&self) -> IntervalStyle

fn float64_ast_dtype(&self) -> DataType

Does the dialect use DOUBLE PRECISION to represent Float64 rather than DOUBLE? E.g. Postgres uses DOUBLE PRECISION instead of DOUBLE

fn utf8_cast_dtype(&self) -> DataType

The SQL type to use for Arrow Utf8 unparsing Most dialects use VARCHAR, but some, like MySQL, require CHAR

fn large_utf8_cast_dtype(&self) -> DataType

The SQL type to use for Arrow LargeUtf8 unparsing Most dialects use TEXT, but some, like MySQL, require CHAR

fn date_field_extract_style(&self) -> DateFieldExtractStyle

The date field extract style to use: DateFieldExtractStyle

fn int64_cast_dtype(&self) -> DataType

The SQL type to use for Arrow Int64 unparsing Most dialects use BigInt, but some, like MySQL, require SIGNED

fn int32_cast_dtype(&self) -> DataType

The SQL type to use for Arrow Int32 unparsing Most dialects use Integer, but some, like MySQL, require SIGNED

fn timestamp_cast_dtype( &self, _time_unit: &TimeUnit, tz: &Option<Arc<str>>, ) -> DataType

The SQL type to use for Timestamp unparsing Most dialects use Timestamp, but some, like MySQL, require Datetime Some dialects like Dremio does not support WithTimeZone and requires always Timestamp

fn date32_cast_dtype(&self) -> DataType

The SQL type to use for Arrow Date32 unparsing Most dialects use Date, but some, like SQLite require TEXT

fn supports_column_alias_in_table_alias(&self) -> bool

Does the dialect support specifying column aliases as part of alias table definition? (SELECT col1, col2 from my_table) AS my_table_alias(col1_alias, col2_alias)

fn requires_derived_table_alias(&self) -> bool

Whether the dialect requires a table alias for any subquery in the FROM clause This affects behavior when deriving logical plans for Sort, Limit, etc.

fn window_func_support_window_frame( &self, _func_name: &str, _start_bound: &WindowFrameBound, _end_bound: &WindowFrameBound, ) -> bool

Allows the dialect to choose to omit window frame in unparsing based on function name and window frame bound Returns false if specific function name / window frame bound indicates no window frame is needed in unparsing

fn full_qualified_col(&self) -> bool

Allow to unparse a qualified column with a full qualified name (e.g. catalog_name.schema_name.table_name.column_name) Otherwise, the column will be unparsed with only the table name and column name (e.g. table_name.column_name)

fn unnest_as_table_factor(&self) -> bool

Allow to unparse the unnest plan as ast::TableFactor::UNNEST.