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

Support a Dial overload that fails right away on ERROR_FILE_NOT_FOUND #34

Open
shueybubbles opened this issue Jun 6, 2023 · 1 comment · May be fixed by #35
Open

Support a Dial overload that fails right away on ERROR_FILE_NOT_FOUND #34

shueybubbles opened this issue Jun 6, 2023 · 1 comment · May be fixed by #35

Comments

@shueybubbles
Copy link

For named pipe connections to SQL Server we don't want to wait for the server to create the pipe, it needs to already exist.
@shueybubbles
Copy link
Author

@aeckleder @natefinch is this repo no longer active for PRs? If so, do you know of an alternative named pipe implementation I should look at for our SQL Server client?

@shueybubbles shueybubbles linked a pull request Jun 6, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add DialExisting shueybubbles/npipe
1 participant
@shueybubbles