This is a very small feature request.
Everything else about the Create Database GUI is sticky -- when changed it stays changed -- EXCEPT the file patterns. Would it be possible to make the file patterns sticky as well?
I often need to create a new database repeatedly since I'm using XQuery to test output from XSLT processes during development. Remembering to add all the file patterns is not excessively burdensome but I would like to not have to do it.
Thanks! Graydon
Hi Graydon,
In the BaseX GUI dialog, some options are pure GUI options, and others, such as CREATEFILTER, are standard database options. The latter ones are discarded, as they would also affect other BaseX instances, such as the standalone mode. If you finish a GUI dialog operation, you can have a look at the Info View panel, in which those options will be listed. They are assigned via the SET command.
If you want to make database options persistent, you can manually add them at the bottom of the .basex configuration file [1]. It’s recommendable to quit the GUI before editing the file, as the graphical user interface might overwrite your changes when it’s closed.
Hope this helps, Christian
[1] https://docs.basex.org/wiki/Configuration#Configuration_Files
On Thu, May 7, 2020 at 6:11 PM Graydon Saunders graydonish@gmail.com wrote:
This is a very small feature request.
Everything else about the Create Database GUI is sticky -- when changed it stays changed -- EXCEPT the file patterns. Would it be possible to make the file patterns sticky as well?
I often need to create a new database repeatedly since I'm using XQuery to test output from XSLT processes during development. Remembering to add all the file patterns is not excessively burdensome but I would like to not have to do it.
Thanks! Graydon
On Mon, May 11, 2020 at 09:23:34AM +0200, Christian Grün scripsit:
Hi Graydon,
Hi Christian --
[sensible reasons for why it does that snipped]
If you want to make database options persistent, you can manually add them at the bottom of the .basex configuration file [1]. It’s recommendable to quit the GUI before editing the file, as the graphical user interface might overwrite your changes when it’s closed.
So if I edit ~/.basex so that the last lines are:
# Local Options ARCHIVENAME = true
# create databases CREATEFILTER = *.xml,*.met ADDARCHIVES = false CHOP = false INTPARSE = true
ADDARCHIVES works, CHOP works, INTPARSE works, but CREATEFILTER does not, or at least I still get only "*.xml" as a suffix in the "File Patterns" box.
Am I doing this wrong? This is with 9.3.2.
Thanks! Graydon
ADDARCHIVES works, CHOP works, INTPARSE works, but CREATEFILTER does not, or at least I still get only "*.xml" as a suffix in the "File Patterns" box.
I found out why this doesn’t work: In the database creation dialog, CREATEFILTER depends on the input format (XML, JSON, etc.). It is always overwritten when the dialog is opened and when this value is changed. Well… I’ll think about that.
On Mon, May 11, 2020 at 10:49:10PM +0200, Christian Grün scripsit:
ADDARCHIVES works, CHOP works, INTPARSE works, but CREATEFILTER does not, or at least I still get only "*.xml" as a suffix in the "File Patterns" box.
I found out why this doesn’t work: In the database creation dialog, CREATEFILTER depends on the input format (XML, JSON, etc.). It is always overwritten when the dialog is opened and when this value is changed. Well… I’ll think about that.
Thank you!
-- Graydon
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Graydon -
Graydon Saunders