Member Junction
    Preparing search index...

    The lexical rules of a dialect: how its text splits into tokens. These decide where string literals, quoted identifiers and comments begin and end, which is what every safe scan of SQL text (stacked statements, comment markers, keyword searches) depends on.

    Index

    Properties

    AlternativeQuotingPrefixes: readonly string[]

    Prefixes of Oracle-style alternative quoting (q'[…]', nq'{…}'), matched ignoring case. The character after the quote is the delimiter: [, {, < and ( close with their partner, any other character closes with itself, always followed by a quote. Empty when the dialect has no alternative quoting.

    BackslashEscapesDependOnServerSettings: boolean

    Whether a server or session setting can turn backslash escapes in string literals on or off (MySQL's NO_BACKSLASH_ESCAPES SQL mode, Spark's spark.sql.parser.escapedStringLiterals). When true, text reading a string literal that contains a backslash cannot know where the literal ends, so a screen should refuse it.

    BlockComments: BlockCommentRules

    Block comment behaviour.

    DollarQuotedStrings: DollarQuoting

    Dollar-quoted string literals.

    IdentifierQuotes: readonly IdentifierQuoteForm[]

    Identifier quoting forms, in the order they are tried.

    LineComments: readonly LineCommentForm[]

    Line comment openers.

    ParameterPlaceholders: readonly ParameterPlaceholderForm[]

    Parameter placeholder forms.

    StringLiterals: readonly StringLiteralForm[]

    String literal forms, in the order they are tried.

    UnquotedIdentifierCase: IdentifierCaseFolding

    What happens to an unquoted identifier's case.