[basex-talk] // versus /*/

Do these have the same meaning? Might there be a subtle distinction, or might they be read differently but functionally identical? > > xquery /*/book[@id="bk112"] Galos, Mike Visual Studio 7: A Comprehensive Guide Computer 49.95 2001-04-16 Microsoft Visual Studio 7 is explored in

Re: [basex-talk] get list of databases

thanks, worked perfectly. On 2019-10-06 3:42 p.m., Christian Grün wrote: Try new List().execute(ctx); See [1] for details. Cheers, Christian [1] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/basex/core/cmd/List.java#L28

Re: [basex-talk] get list of databases

Try new List().execute(ctx); See [1] for details. Cheers, Christian [1] https://github.com/BaseXdb/basex/blob/master/basex-core/src/main/java/org/basex/core/cmd/List.java#L28 thufir schrieb am Mo., 7. Okt. 2019, 00:35: > Hi, > > pardon the silly question, but how do I get a list of

[basex-talk] get list of databases

Hi, pardon the silly question, but how do I get a list of databases exactly? I'm looking at: https://github.com/BaseXdb/basex/blob/master/basex-examples/src/main/java/org/basex/examples/local/CreateCollection.java and want output like: > list Name Resources Size Input Path

Re: [basex-talk] Migrating ~ 3M record db from BaseX to PostgreSQL results in OOM

Some complementary notes (others may be able to tell you more about their experiences with large data sets): a GiST index would have to be built there, to allow full-text searches; > PostgreSQL is picked > You could as well have a look at Elasticsearch or its predecessors. there might be a leak

[basex-talk] Migrating ~ 3M record db from BaseX to PostgreSQL results in OOM

Hello, This is essentially part2 of trying to index large amounts of web data. To summarize what happened before: The initial discussion started here [1], Christian suggested some options, I dove into each of them, I realized that doing this on a low-memory system is harder than I initially

Re: [basex-talk] basex OOM on 30GB database upon running /dba/db-optimize/

Regarding selective full-text indexing, I just tried XQUERY db:optimize("linuxquestions.org-selective", true(), map { 'ftindex': true(), 'ftinclude': 'div table td a' }) And I got OOM on that, the exact stacktrace attached in this message. I will open a separate thread regarding migrating the

Re: [basex-talk] basex OOM on 30GB database upon running /dba/db-optimize/

The current full text index builder provides a similar outsourcing mechanism to that of the index builder for the default index structures; but the meta data structures are kept in main-memory, and they are more bulky. There are definitely ways to tackle this technically; it hasn't been of high