-
Notifications
You must be signed in to change notification settings - Fork 27
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
Socket file path is too long #50
Comments
Proposed solution: socket file location should be a configuration option with a sensible default. |
I believe it should work for me - will try it out; I think adding a Thanks!
On Tue, Dec 2, 2014 at 11:48 AM, Yegor Bugayenko [email protected]
|
yeah, totally agree. would you be interested to submit a pull request? |
After moving mysql data under /tmp, following the advice in #10 , I found that Hibernate started giving errors like these:
So I created a patch to let me put just the socket file under /tmp: #51. |
@rultor release, tag is |
@seanf version 0.9 is in Maven Central already. many thanks for your contribution! |
@sbelov please close the issue if the solution is good enough |
@sbelov ping... |
FWIW, I did see the temp table problem (#50 (comment)) again, but not since I started using the new |
If the maven module is built in a deep enough directory location, and
<data/>
configuration setting points to somewhere inside${project.build.directory}
(which is the default), MySQL will not start due to failure to open a Unix socket (see below).A workaround is to point
<data/>
to a fixed location with a shorter path (say, under /tmp). But I'd still like to be able to have my data under${project.build.directory}
, so that all mysql files are properly deleted on executingmvn clean
.The text was updated successfully, but these errors were encountered: