Package io.opentelemetry.instrumentation.api.incubator.semconv.db

Class SqlDialect

java.lang.Object

io.opentelemetry.instrumentation.api.incubator.semconv.db.SqlDialect

public abstract class SqlDialect
extends Object

Describes SQL dialect options that affect how SqlQueryAnalyzer processes queries.

Field Summary

Fields

Modifier and Type	Field	Description
static final SqlDialect	DOUBLE_QUOTES_ARE_IDENTIFIERS	Dialect where double-quoted fragments are treated as identifiers (e.g. column/table names) and therefore left intact during sanitization.
static final SqlDialect	DOUBLE_QUOTES_ARE_STRING_LITERALS	Dialect where double-quoted fragments are treated as string literals and therefore sanitized (replaced with ?).

Method Summary

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details

DOUBLE_QUOTES_ARE_STRING_LITERALS

public static final SqlDialect DOUBLE_QUOTES_ARE_STRING_LITERALS

Dialect where double-quoted fragments are treated as string literals and therefore sanitized (replaced with ?).

This is a safer choice if you don't know how the database interprets double-quoted tokens. If the database actually uses double quotes for identifiers, the downside is that identifier names are replaced with ?, reducing diagnostic clarity. By contrast, choosing DOUBLE_QUOTES_ARE_IDENTIFIERS incorrectly would fail to sanitize sensitive string-literal values.

DOUBLE_QUOTES_ARE_IDENTIFIERS

public static final SqlDialect DOUBLE_QUOTES_ARE_IDENTIFIERS

Dialect where double-quoted fragments are treated as identifiers (e.g. column/table names) and therefore left intact during sanitization. Use this only for databases where double quotes always denote identifiers.