Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

clientOsUserName is not passed #58

Closed
sarg opened this issue Apr 21, 2022 · 2 comments · Fixed by #62
Closed

clientOsUserName is not passed #58

sarg opened this issue Apr 21, 2022 · 2 comments · Fixed by #62
Assignees
@kaklakariada
Labels
bug Unwanted / harmful behavior

Comments

@sarg
Copy link

sarg commented Apr 21, 2022

When I connect to exasol via the go driver I can see that os_user is empty in select * from exa_user_sessions;
@kaklakariada kaklakariada added the bug Unwanted / harmful behavior label Apr 25, 2022
kaklakariada added a commit that referenced this issue Apr 26, 2022
@kaklakariada
#58: Fix missing OS username
8aa5604
@kaklakariada kaklakariada mentioned this issue Apr 26, 2022
Merged
@kaklakariada kaklakariada self-assigned this Apr 26, 2022
@kaklakariada
Copy link
Collaborator

Hi @sarg,
thank you very much for your ticket and the pull request!
In order to speedup things I created a separate PR #62 with your fix, additional integration tests and changelog.

kaklakariada added a commit that referenced this issue Apr 27, 2022
@kaklakariada
#58: Fix missing OS username (#62)
b28f526 
* #58: Fix missing OS username
@kaklakariada
Copy link
Collaborator

Hi @sarg,
I just release v0.3.3 including this bugfix.
Thanks again for your help!

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

@kaklakariada kaklakariada

Labels
bug Unwanted / harmful behavior
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#58: Fix missing OS username exasol/exasol-driver-go
2 participants
@sarg @kaklakariada