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

console and studio DB create commands don't honor server.database.path setting v1.3.0 #1235

Closed
8forty opened this issue Dec 28, 2012 · 4 comments
Assignees
Milestone

Comments

@8forty
Copy link

8forty commented Dec 28, 2012

I've confirmed in Studio that I have a server.database.path set to a good directory when running server.sh. But when I create a database (with studio or console "create database ..." command) it always appears in the orientdb-home/databases directory.

@kadeng
Copy link

kadeng commented Nov 15, 2013

A short analysis of this problem, which I also noticed in 1.6.0 and 1.6.1-SNAPSHOT (as checked out today from 1.6.1-hotfix branch)

OServerConfiguration.getStoragePath(..) should honor the server.database.path setting. Instead, it returns null, which leads OBinaryNetworkProtocolAbstract.getDatabaseInstance(..) to set the default path (i.e. orientdb-home/databases).

@ghost ghost assigned lvca Nov 16, 2013
@lvca
Copy link
Member

lvca commented Nov 16, 2013

Thanks for the bug tracking, I moved it in 1.6.1.

lvca added a commit that referenced this issue Nov 16, 2013
@lvca lvca closed this as completed Nov 16, 2013
@kadeng
Copy link

kadeng commented Nov 16, 2013

The fix works. At first It seemed not to, but that was due to a directory access rights issue.

@lvca
Copy link
Member

lvca commented Nov 17, 2013

Great

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants