On Wed, 2022-02-23 at 23:09 +0100, Christian Grün wrote:
Returning to the thought of a feature request, let me suggest that
adding switches to the command-line tool
We could add an option for preventing BaseX to read and write the initial configuration file, but we'd then still need to define a home directory in which new databases, users, jobs, etc. are stored. How would you handle that?
My first thought would be simply to expose to the command line the flag in the constructor you had referenced.
The base case for an embedded database has no user model, and supports creation of new databases only through the target path. However, such differences might press the limits of a benign request.
If a target path is needed beyond the database itself, then it might be passed on the command line. Alternatively, a special directory layout might be considered which encloses both the database files and the auxiliary configuration files, as peer sub-directories in the same parent, following a static layout utilized only when the application is invoked in some special mode.
Have you already checked out the Configuration article in our Wiki that has been referenced multiple times in this thread?
Yes, but it doesn't mean I understand quite yet how all the parts fit together. Does it seem I missed or misunderstood something?