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.

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

Crash when database connection is via socket (so no host) #128

Open
brucek2 opened this issue Jun 5, 2020 · 0 comments
Open

Crash when database connection is via socket (so no host) #128

brucek2 opened this issue Jun 5, 2020 · 0 comments

Comments

@brucek2
Copy link

brucek2 commented Jun 5, 2020

It looks like src/GetDatabaseConfig:34 assumes there will be a 'host' index defined in the $connection array, although this will not be the case for a connection via socket vs. TCP/IP.

This is a bummer because it means if I want backup-manager/laravel installed I am forced to use the higher overhead TCP/IP connection for all of my application, even though the socket connection works fine for the rest of my Laravel app when backup-manager/laravel is not installed.

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

No branches or pull requests

1 participant