Struct sqlparser::dialect::RedshiftSqlDialect

pub struct RedshiftSqlDialect {}

Trait Implementations

impl Debug for RedshiftSqlDialect

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Dialect for RedshiftSqlDialect

fn is_proper_identifier_inside_quotes(&self, chars: Peekable<Chars<'_>>) -> bool

Determine if quoted characters are proper for identifier It’s needed to distinguish treating square brackets as quotes from treating them as json path. If there is identifier then we assume there is no json path.

fn is_delimited_identifier_start(&self, ch: char) -> bool

Determine if a character starts a quoted identifier. The default implementation, accepting “double quoted” ids is both ANSI-compliant and appropriate for most dialects (with the notable exception of MySQL, MS SQL, and sqlite). You can accept one of characters listed in Word::matching_end_quote here

fn is_identifier_start(&self, ch: char) -> bool

Determine if a character is a valid start character for an unquoted identifier

fn is_identifier_part(&self, ch: char) -> bool

Determine if a character is a valid unquoted identifier character

fn supports_filter_during_aggregation(&self) -> bool

Does the dialect support FILTER (WHERE expr) for aggregate queries?

fn parse_prefix(
    &self,
    _parser: &mut Parser<'_>
) -> Option<Result<Expr, ParserError>>

Dialect-specific prefix parser override

fn parse_infix(
    &self,
    _parser: &mut Parser<'_>,
    _expr: &Expr,
    _precendence: u8
) -> Option<Result<Expr, ParserError>>

Dialect-specific infix parser override

fn get_next_precedence(
    &self,
    _parser: &Parser<'_>
) -> Option<Result<u8, ParserError>>

Dialect-specific precedence override

fn parse_statement(
    &self,
    _parser: &mut Parser<'_>
) -> Option<Result<Statement, ParserError>>

Dialect-specific statement parser override