feat(database): Capture query data behind dataCollection

Inizia dal percorso JDBC P6Spy StatementInformation.getSql() e dalle integrazioni Android SupportSQLite e SQLiteDriver, tracciando dove è disponibile databaseQueryData. Usa i casi elencati di abilitato/disabilitato, forma dei parametri, dimensione, batch e argomenti di binding Android per definire la copertura; completato significa una raccolta limitata al tempo di origine senza modificare i campi di query sanificati, oltre alla documentazione delle categorie supportate.

Problem

The Java SDK exposes dataCollection.databaseQueryData, but the current first-party database integrations do not collect any of the value-bearing data controlled by that option:

• JDBC records the original statement text through P6Spy's StatementInformation.getSql(), not bound parameter values.
• Android SQLite receives bind arguments but does not attach them to spans.
• Neither integration captures write payloads or returned result data.

As a result, databaseQueryData currently has no production consumer in these integrations.

Sanitized or parameterized db.query.text, db.query.summary, and structural database metadata are intentionally outside this option and should continue to be collected independently.

Proposal

In the next major version, add source-time collection of supported database query data and guard it with dataCollection.databaseQueryData.

Start with the value-bearing data already available to first-party instrumentation:

• JDBC prepared/callable statement bind values, where P6Spy exposes them safely.
• Android SQLite bind arguments in the SupportSQLite and SQLiteDriver integrations.

Evaluate write-operation payloads and returned result data separately; only add them where useful, bounded, and supported by established Sentry span conventions.

Requirements

• Apply the policy when first-party instrumentation writes the data, not later during serialization or export.
• Do not put bound values into span descriptions, span names, db.query.text, or db.query.summary.
• Use standardized structured span attributes for parameters where available, such as db.query.parameter.<key>.
• databaseQueryData=false must prevent value-bearing query data from being attached.
• Query text must remain sanitized/parameterized independently of this option.
• Add size/count limits and fail-closed handling for unsupported or malformed values.
• Preserve explicitly supplied customer span data.
• Add tests for enabled/disabled behavior, positional and named parameters, null/binary/large values, batch operations, and Android bind arguments.
• Document which integrations and database data categories are supported.

Related

• Data Collection specification: databaseQueryData controls bound query parameters, write-operation payloads, and returned result data.
• SQL sanitization and db.query.summary generation are separate concerns and should not be made conditional on this option.