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

If SS_DATABASE_SERVER is "localhost" don't assume that mysql.sock is okay #22

Open
IgorNadj opened this issue Aug 18, 2014 · 0 comments
Open

If SS_DATABASE_SERVER is "localhost" don't assume that mysql.sock is okay #22

IgorNadj opened this issue Aug 18, 2014 · 0 comments
Labels
affects/v4 complexity/medium impact/low type/bug

Comments

@IgorNadj
Copy link

Right now, if SS_DATABASE_SERVER is set to "localhost" then it assumes that using mysql.sock is okay. If the database is running as TCP-only, this causes sspak to fail.

PHP itself will connect using TCP, and so this creates a situation where sspak's semantics differ from SilverStripe's, which is a bug.

Make sspak interpret localhost as a TCP connection when calling mysql.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects/v4 complexity/medium impact/low type/bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Cheddam @IgorNadj @emteknetnz