fix(server-utils): Keep qualified table names in db.query.summary - #23853
Merged
Lms24 merged 2 commits intoSep 8, 2026
Conversation
Contributor
size-limit report 📦
|
Lms24
force-pushed
the
lms/fix-core-qualified-table-names-in-query-summary
branch
2 times, most recently
from
September 3, 2026 07:26
870b4cb to
d8b3134
Compare
Lms24
marked this pull request as ready for review
September 3, 2026 07:52
Member
|
I just double checked if we can unskip the |
`getSqlQuerySummary` matched a quoted table reference with a regex that stopped after the first quoted identifier, so a schema-qualified name lost its table part (`SELECT ... FROM "public"."User"` summarized as `SELECT "public"`) and a JOIN of two tables in the same schema collapsed into two identical targets. The INSERT/UPDATE/DELETE/DDL branches used a different, whitespace-delimited pattern that kept the qualified name but split any quoted identifier containing a space (`INSERT INTO "my table"` summarized as `INSERT "my`). Both branches now build on one identifier pattern that treats each quoted or bare part as a unit and allows dot-qualification. This matters more now that the value is promoted into span names, where two tables that differ only by table part are otherwise indistinguishable. Refs #23676 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ble names The Prisma v5/v6/v7 suites asserted `SELECT "public"` for a schema-qualified table, which encoded the truncation the previous commit fixes. Refs #23676 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Lms24
force-pushed
the
lms/fix-core-qualified-table-names-in-query-summary
branch
from
September 8, 2026 12:06
d8b3134 to
f194e79
Compare
Lms24
changed the title
db.query.summarydb.query.summary
JPeer264
approved these changes
Sep 8, 2026
Lms24
deleted the
lms/fix-core-qualified-table-names-in-query-summary
branch
September 8, 2026 13:01
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
getSqlQuerySummaryused two different regexes to find the table name, and each got it wrong in a different way.The SELECT/JOIN path matched one quoted identifier and stopped, so it dropped everything after the first dot. The INSERT/UPDATE/DELETE/DDL path split on whitespace, so it kept the dotted name but cut quoted names containing a space in half. Both now use one pattern: quoted-or-bare parts joined by dots.
SELECT ... FROM "public"."User"SELECT "public"SELECT "public"."User"SELECT ... FROM "public"."A" JOIN "public"."B"SELECT "public" "public"SELECT "public"."A" "public"."B"INSERT INTO "my table" ...INSERT "myINSERT "my table"DELETE FROM "public"."User"DELETE "public"."User"Refs #23676