Struct datafusion_sql::unparser::dialect::MySqlDialect
source · pub struct MySqlDialect {}
Trait Implementations§
source§impl Dialect for MySqlDialect
impl Dialect for MySqlDialect
source§fn identifier_quote_style(&self, _: &str) -> Option<char>
fn identifier_quote_style(&self, _: &str) -> Option<char>
Return the character used to quote identifiers.
source§fn supports_nulls_first_in_sort(&self) -> bool
fn supports_nulls_first_in_sort(&self) -> bool
Does the dialect support specifying
NULLS FIRST/LAST
in ORDER BY
clauses?fn interval_style(&self) -> IntervalStyle
source§fn utf8_cast_dtype(&self) -> DataType
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
source§fn large_utf8_cast_dtype(&self) -> DataType
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
source§fn date_field_extract_style(&self) -> DateFieldExtractStyle
fn date_field_extract_style(&self) -> DateFieldExtractStyle
The date field extract style to use:
DateFieldExtractStyle
source§fn int64_cast_dtype(&self) -> DataType
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
source§fn timestamp_cast_dtype(
&self,
_time_unit: &TimeUnit,
_tz: &Option<Arc<str>>,
) -> DataType
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
source§fn use_timestamp_for_date64(&self) -> bool
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
source§fn float64_ast_dtype(&self) -> DataType
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
Auto Trait Implementations§
impl Freeze for MySqlDialect
impl RefUnwindSafe for MySqlDialect
impl Send for MySqlDialect
impl Sync for MySqlDialect
impl Unpin for MySqlDialect
impl UnwindSafe for MySqlDialect
Blanket Implementations§
source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more