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

Permissions on "db" should not be checked if SQLite isn't used #773

Closed
anno1337 opened this issue Jul 21, 2014 · 1 comment
Closed

Permissions on "db" should not be checked if SQLite isn't used #773

anno1337 opened this issue Jul 21, 2014 · 1 comment
Labels
Improvement
Milestone
1.9.0

Comments

@anno1337
Copy link
Contributor

When MySQL or any other database is used instead of SQLite there is no need for the db directory to exist or let alone to be writable.

Yet the check for it to be writeable happens anyway. I'd suggest bypassing the check in case SQLite isn't used.
@nicosomb
Copy link
Member

You're right, we have to change this behaviour.

@nicosomb nicosomb added this to the 1.x milestone Jul 21, 2014
This was referenced Jul 21, 2014
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Improvement
Projects
None yet
Milestone
1.9.0
Development

Successfully merging a pull request may close this issue.

Proposed fix for #773
2 participants
@nicosomb @anno1337