Apparently that was the mistake.
Thank you!
Marc
On Mon, 5 Jun 2017, Christian Grün wrote:
Did you differentiate between global and local options [1]?
Cheers,
Christian
[1] http://docs.basex.org/wiki/Options
Am 05.06.2017 5:39 nachm. schrieb :
Options manually added to the .basex co
Did you differentiate between global and local options [1]?
Cheers,
Christian
[1] http://docs.basex.org/wiki/Options
Am 05.06.2017 5:39 nachm. schrieb :
Options manually added to the .basex config file are deleted by BaseX.
For example, these Create Options all get deleted from the .basex fil
Options manually added to the .basex config file are deleted by BaseX.
For example, these Create Options all get deleted from the .basex file
after running a standalone basex script:
ADDARCHIVES = true
CREATEFILTER = *.anx
STRIPNS = true
INTPARSE = true
LANGUAGE = Dutch (also tried 'nl')
Bas
Dear Radim,
Welcome to the list.
> 1) BaseX GUI is automatically opened with administration permissions without
> any login request. Can it be fixed?
As the GUI has been designed for local standalone usage, no user can
be specified. If you plan to use BaseX in a distributed environment,
the DBA
Hello,
we would like to build our database application on BaseX in our company.
However, we would need to solve following issues we encountered with.
1) BaseX GUI is automatically opened with administration permissions without
any login request. Can it be fixed?
2) Once user is created in
5 matches
Mail list logo