In the streaming branch, the data dict (db.params, db.paramstyle, db.executemany, db.cursor) is built but never attached to the span — only sentry.origin and sentry.op are set as attributes. The legacy branch (else) correctly applies them via span.set_data(k, v). As a consequence, when trace_lifecycle == 'stream' is enabled, SQL spans lose all parameter/cursor/executemany diagnostic information that users rely on for debugging, while the same instrumentation works on the non-streaming path. This is a behavioral regression that silently degrades observability on the streaming code path.

query = _format_sql(cursor, query) returns real_sql or to_string(sql) (tracing_utils.py:513). to_string typically does not return None for non-None input, and even if sql is None, to_string(None) would yield the string 'None' rather than None. Therefore the "<unknown SQL query>" if query is None else query guard is essentially dead code for the documented inputs. More importantly, an empty string query ("") — a plausible degenerate input — would still be used as the span name instead of the fallback because the check is is None rather than a truthiness check, leading to spans named with an empty string.