Skip to content

refactor(database) :: decode rows into named columns first - #1595

Merged
lovasoa merged 2 commits into
mainfrom
81reap/sqlx-next/3-row-columns
Nov 12, 2026
Merged

lovasoa merged 2 commits into
mainfrom
81reap/sqlx-next/3-row-columns

Conversation

@81reap

@81reap 81reap commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator

Behavior does not change.

Refs #1056


Stack created with GitHub Stacks CLI • Give Feedback 💬

@81reap
81reap added this pull request to stack #1599 November 12, 2026 06:22

@lovasoa lovasoa left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason for the change? the old implementation sounds cleaner, doesn't it? we don't need to allocate an intermediary vector here

@lovasoa
lovasoa force-pushed the 81reap/sqlx-next/3-row-columns branch from 9570169 to 26176ab Compare November 12, 2026 09:48
@81reap

81reap commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator Author

This is mostly a refactor to support the feature flagged dialup stratgey. Thread here :: #1597 (comment)

@lovasoa

lovasoa commented Nov 12, 2026

Copy link
Copy Markdown
Collaborator

it looks like the refactor does not pay for itself in it's current form. It just creates an intermediary vec that's not needed

Base automatically changed from 81reap/sqlx-next/2-connection-setup to main November 12, 2026 22:07
@lovasoa
lovasoa force-pushed the 81reap/sqlx-next/3-row-columns branch 2 times, most recently from 304df7e to d0d9df0 Compare November 12, 2026 22:47
@lovasoa
lovasoa force-pushed the 81reap/sqlx-next/3-row-columns branch from d0d9df0 to 54a2320 Compare November 12, 2026 22:51
@lovasoa
lovasoa enabled stacked auto-merge November 12, 2026 22:53
@lovasoa
lovasoa added this pull request to the merge queue Nov 12, 2026
Merged via the queue into main with commit 4cb43af Nov 12, 2026
21 checks passed
@81reap

81reap commented Nov 13, 2026 •

Copy link
Copy Markdown
Collaborator Author

we can revert if you'd like, I don't mind waiting for more thoughts on this :)

creates an intermediary vec

jsut an opinion, but to me this is part of writing readable PRs. I want to take the intermediate fluff and refactors out of the meat and potatos so that we can make sure the important stuff is semantically correct

@lovasoa

lovasoa commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

Yes, refactoring is welcome ! I did keep your extraction of the key-value logic into a separate function, but removed the unneeded allocation of an intermediary vector. 54a2320

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants