Hi Christian,
Using 6.6.3 does solve the default directory creation but it still does not respect the SET DBPATH for execution. What I also noticed was that after I start the basexserver I can change the .basex file on the fly and the clientsession in the app will then reflect that change. So something still seems to give the .basex dbpath value precedence. Interestingly the logs are recording and locked using the directory from -c"SET DBPATH..." even when I change the .basex file.
Here's the command I was using to start it up. Makes no difference if I replace basex-6.6.3-SNAPSHOT.jar in the basexserver.bat either.
C:\BaseX\bin>java -cp C:\basex\basex-6.6.3-SNAPSHOT.jar org.basex.BaseXServer -p1985 -c"SET DBPATH C:/BaseX/BaseXData;info" General Information Database Path: C:/BaseX/BaseXData Used Main Memory: 1129 KB
Database Creation Whitespace Chopping: ON Entity Parsing: OFF
Indexes Path Summary: ON Text Index: ON Attribute Index: ON Full-Text Index: OFF BaseX 6.6.3 beta [Server] Server was started.
Jason
-----Original Message----- From: Christian Grün [mailto:christian.gruen@uni-konstanz.de] Sent: May-17-11 3:54 AM To: Jennifer Violago; Jason Klassen Subject: Re: [basex-talk] BaseXServer.bat not respecting the -c"SET DBPATH ..." option?
Dear Jason,
I had a quick look into the code base; the commands (specified by -c) were executed after having initialized the server instance. As a consequence, the default database directory was created before parsing the DBPATH option.
I decided to switch the execution order: the specified commands will now be executed before initializing the logger (which is responsible for creating the database/.logs directory, and locking that folder). Feel free to give us some feedback on the latest 6.6.3 snapshot of BaseX (which is as stable as the official release):
http://files.basex.org/releases/latest/
Hope this helps, Christian