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,
> 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 o
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
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
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
te
5 matches
Mail list logo
