feat(lakebase): add ability to lookup DB username with API#123
Merged
Conversation
pkosiec
force-pushed
the
pkosiec/lakebase-plugin
branch
3 times, most recently
from
c16ad89 to
ed174de
Compare
pkosiec
changed the title
This was referenced Feb 23, 2026
pkosiec
force-pushed
the
pkosiec/lakebase-plugin
branch
from
ed174de to
a17ec82
Compare
pkosiec
force-pushed
the
pkosiec/lakebase-plugin
branch
from
a17ec82 to
20c9a3a
Compare
MarioCadenas
approved these changes
Feb 24, 2026
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
2 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.
Why?
It is used by the upcoming Lakebase driver.
I didn't want to make it default behavior as I'm not sure if calling the API would be expected by the user by default. Also, I didn't want to break the API and change
createLakebasePoolI()to return a promise.