Hi Alex,
Please note that our event handling may be removed in a future 8.x
version of BaseX. It may be replaced by a server-side trigger
mechanism.
I would like to hear if you, or anyone else, are using BaseX events in
any productive systems?
Cheers,
Christian
On Sun, May 17, 2015 at 7:30 PM
The behavior is correct indeed. But I agree it is surprising, and it
has not properly been documented so far:
> declare option output:json "lax";
This is a shortcut for "lax=true". Thus, the boolean value will always
be appended in the string representation, no matter if it has been
specified in
Hi!
Maybe this has been answered before, but is it possible to open and read a
database located outside DBPATH?
Kind regards
Ketill Fenne
Hi Ketill,
> Maybe this has been answered before, but is it possible to open and read a
> database located outside DBPATH?
Sorry, no. Currently, what you can do is..
* set DBPATH via system properties before starting BaseX [1],
* create symbolic links in your database directory, or
* copy your d
Ok, thanks!
My requirement is that in a locally installed product that uses BaseX to
store content I need to read a database(s) containing new/changed documents
from (preferrably) an upgrade/ - folder and add/replace documents in the
existing database(s) in the DBPATH - dir.
I guess I'll move the
Hi Ketill,
I don't fully understand your requirement. Why don't you simply add/replace
the documents (using the database commands or within XQuery db:add(...) or
db:replace(...)). This, of course, reads files from the file system to add
them to the database.
It looks much more suitable for the us
Hi!
The only reason is that we are currently moving the product from using
Oracle Berkeley XMLDB to BaseX, and would like to leave as much of the
existing java-code as is :-)
Ketill
On Mon, May 18, 2015 at 10:51 AM, Dirk Kirsten wrote:
> Hi Ketill,
>
> I don't fully understand your requirement.
Hello Hans-Jürgen,
It has been a while, but the erroneous behavior of the base-uri
declaration should now be history (if it doesn't sound too pathetic).
A new snapshot will be available later today..
Regarding the declaration of invalid paths (e.g. with multiple parent
references), my impression
Hi Christian,
I have a problem and I cannot understand what’s happening.
I have set UPDINDEX to true, then I have created a database with some XML files
in the BaseXGUI. When I look at the DB properties, both Up-to-date and UPDINDEX
are true (this is what I want). But if I add some more XML fil
Hi Javier,
> But if I add some more XML files, using the Add Ressources at the Properties
> window, the Up-to-date flag becomes false (!) and I cannot understand why.
The reason is that UPDINDEX won't update all available index and
statistics in BaseX. I have added an explanatory line in [1].
H
Hi all,
Database created from 17692 MB: resulting DB size 30450 MB.
CHOP is set to false, but for good reasons. TEXTINDEX and ATTRINDEX are true,
but FTINDEX false.
Can I just sanity check this size of DB? It surprises me a little.
(Basex 8.0.2 by the way).
Thanks in advance,
Constantine
__
> Hi all,
>
> Database created from 17692 MB: resulting DB size 30450 MB.
>
> CHOP is set to false, but for good reasons. TEXTINDEX and ATTRINDEX are
> true, but FTINDEX false.
The CHOP flag may be the reason, because each whitespace text node
will now be stored as individual XML node (this can d
I am running a web script in two identical versions (identical as in "cut
and paste"), one via RESTXQ and one vi REST. The response is different, and
I wondered what may be the trouble.
For example the output (the URLs only works locally) for
http://ljohnsen:8984/hyphens/mellom
is the same as
Hi Lars,
hm, that's difficult to tell. All I can say is that this sounds
unusual, so I'm coming up with my standard questions: Do you think you
could build us a little example that allows us to reproduce the
problem? Have you tried the latest version of BaseX?
Best,
Christian
On Mon, May 18, 20
Hi Christian - and thanks for fast response. Latest version 8.11 is in use
(same behaviour as previous). Let me see if I can make a self contained
example.
best,
Lars
2015-05-18 13:40 GMT+02:00 Christian Grün :
> Hi Lars,
>
> hm, that's difficult to tell. All I can say is that this sounds
> unus
Tried to make a small example but then things worked the same, so reindexed
the database (no language and no stemming) and found this. It seems that it
has to to with character encoding.
RESTXQ finds hits for "føre" as "fore" while REST treats it as "føre" so
the outputs are like this
REST output
It could be that your URL is decoded in a wrong way.. What happens if
you run the following function with REST and RESTXQ and "føre" as
word?
declare
%rest:path("/test/encoding/{$word}")
function page:test-encoding($word) {
string-to-codepoints($word)
};
Thanks,
Christian
string-t
The codepoints are identical for both for "føre":
102 248 114 101
and same as GUI.
However, when using text index instead of full text the results are the
same for both, except that RESTXQ takes almost forever (as if there was no
text index), while REST gives immediate result. So it looks as if
> However, when using text index instead of full text the results are the same
> for both, except that RESTXQ takes almost forever
What about the original query: Has it been slow as well, or do you
think this is a new problem?
> 2015-05-18 14:28 GMT+02:00 Christian Grün :
>>
>> It could be that
The full text query is blisteringly fast for both, the text index query is
fast only for REST queries and seems not to be used with queries in RESTXQ.
I am rebuilding the whole database now to see how it goes, and will restart
everything for a new assessment.
2015-05-18 15:00 GMT+02:00 Christian
As an update, after rebuilding database with
text index,
full text index (no language, no stemming, keep diacritics)
restarting server:
BaseX 8.1.1 [Server]
Server was started (port: 29084)
[main] INFO org.eclipse.jetty.server.AbstractConnector - Started
SelectChannelConnector@0.0.0.0:8984
HTTP S
I missed the obvious part of option 'suboptions'
I fixed the parsing in basex-stream and now `query.options()` returns an
object in v0.1.2.
A last update, which may illuminate a little. After reindexing the database
using Norwegian (snowball), stemming, and keeping diacritis, RESTXQ
processes neither the special characters (treats them as closest ascii),
nor inflected forms.
The words "mannen" (=the man, definite) and "spaserer" (=wal
23 matches
Mail list logo
