Re: [basex-talk] Bulk import (moving from eXist to BaseX)

2019-01-02 Thread Fabrice ETANCHAUD
Hi Andreas, The CREATE-DB command can create a collection from a directory's structure [1] Best regards, Fabrice ETANCHAUD [1] : http://docs.basex.org/wiki/Commands#CREATE_DB -Message d'origine- De : BaseX-Talk [mailto:basex-talk-boun...@mailman.uni-konstanz.de] De la part de Andreas

[basex-talk] Java XQuery

2019-01-02 Thread thufir
After creating and populating a database: try { new DropDB(databaseName).execute(context); } catch (BaseXException ex) { Logger.getLogger(Database.class.getName()).log(Level.SEVERE, null, ex); LOG.fine("no databases to drop"); } how would I query it?

[basex-talk] upper limits on storage; database admin

2019-01-02 Thread thufir
What are the upper bounds to basex in size? Assuming it's just text xml, gigabytes is quite a bit to my thinking. At a certain, it's "big data" -- but how do you know when you're approaching that point? Or, is the bottleneck more read/write and consistency problems? What little I know of

[basex-talk] XQuery from Java

2019-01-02 Thread thufir
I'm a tad more proficient with BaseX, but, how do I actually build an XQuery? Yes, I can write an XQuery and save it in a text file, then use BaseX for execution. But it would be far more flexible to write the actual XQuery from within Java itself. But how? Oracle gives an example:

Re: [basex-talk] Bulk import (moving from eXist to BaseX)

2019-01-02 Thread Andreas Jung
I decided to implement a direkt exist2basex copy script that allows me to copy over the content through WebDAV from one database to another other with just some Python lines with the benefit to taking care of arbitrary data and not only markup content:

Re: [basex-talk] Scaling and Jsoniq

2019-01-02 Thread Christian Grün
Hi Ben, > First, are there any support plans for scaling outwards? I know MarkLogic has > splits clusters into multiple enodes and dnodes. But the idea is that there > isn't one central bottleneck for requests. BaseX as open source project provides no built-in features for horizontal scaling.

Re: [basex-talk] update:output() update:cache()

2019-01-02 Thread Christian Grün
Dear Dieter, > I do not exactly understand, for which purpose update:output() is meant. > Does anybody have an example, where one can see, how it works? (There is no > example in the docs.) By default, no result can be returned with XQuery Update 1.0 if an update is performed. The update:output

Re: [basex-talk] basic xquery

2019-01-02 Thread Christian Grün
Hi Thufir, You can save this query on disk (e.g. as fetch.xq) and run it "basex fetch.xq". See the Startup section in our documentation [1] to learn how BaseX is used on the command-line. Best, Christian [1] http://docs.basex.org/wiki/Startup On Wed, Jan 2, 2019 at 1:00 AM thufir wrote: >

Re: [basex-talk] Scaling and Jsoniq

2019-01-02 Thread Jonathan Robie
As an author of both JSONiq and XQuery 3.1, I generally think of XQuery 3.1 as the standard that implemented what JSONiq did. Some authors of JSONiq see this very differently, preferring the JSONiq way of doing things. Is there anything JSONiq can do that XQuery 3.1 can't? Jonathan On Wed, Jan

[basex-talk] console usage

2019-01-02 Thread thufir
How can I run this script? thufir@dur:~/basex$ thufir@dur:~/basex$ basex [warning] /usr/bin/basex: Unable to locate /usr/share/java/jing.jar in /usr/share/java BaseX 9.0.1 [Standalone] Try 'help' to get more information. > > RUN fetch.note.text.xq Resource "/home/thufir/fetch.note.text.xq"

Re: [basex-talk] Bulk import (moving from eXist to BaseX)

2019-01-02 Thread Christian Grün
Hi Andreas, In BaseX, you can use the EXPORT command or the db:export function to write all database contents to disk [1,2]. I know too little about eXist-db; maybe they offer a similar feature? After that, as Fabrice indicated, you can use the CREATE DB command to create a database by pointing

Re: [basex-talk] console usage

2019-01-02 Thread Christian Grün
> > RUN fetch.note.text.xq > Resource "/home/thufir/fetch.note.text.xq" not found. Is the script located at this path? If not, you will have to change to this directory and start BaseX from there, or you will need to specify the full path.

Re: [basex-talk] Bulk import (moving from eXist to BaseX)

2019-01-02 Thread Fabrice ETANCHAUD
My mistake Andreas, I completely forgot raw content... By the way, Happy new year to all happy BaseX users, the BaseX team, and to you, Christian ! Best regards, Fabrice -Message d'origine- De : BaseX-Talk [mailto:basex-talk-boun...@mailman.uni-konstanz.de] De la part de Christian

Re: [basex-talk] JSON serialization/compatibility with exist-db JSON?

2019-01-02 Thread Christian Grün
Hi Andreas, Once again I must confess that I don’t know enough about eXist-db. What I can say is that only some JSON features were standardized, and not necessarily the ones that you find in eXist-db, BaseX and other processors (which were implemented much earlier). I have just referenced some

Re: [basex-talk] console usage

2019-01-02 Thread thufir
On 2019-01-02 8:07 a.m., Christian Grün wrote: > RUN fetch.note.text.xq Resource "/home/thufir/fetch.note.text.xq" not found. Is the script located at this path? If not, you will have to change to this directory and start BaseX from there, or you will need to specify the full path.

Re: [basex-talk] console usage

2019-01-02 Thread thufir
On 2019-01-02 8:01 a.m., thufir wrote: Resource "/home/thufir/fetch.note.text.xq" not found. O My pwd is /home/thufir/basex which is where the script is..

Re: [basex-talk] console usage

2019-01-02 Thread thufir
On 2019-01-02 8:07 a.m., Christian Grün wrote: > RUN fetch.note.text.xq Resource "/home/thufir/fetch.note.text.xq" not found. Is the script located at this path? If not, you will have to change to this directory and start BaseX from there, or you will need to specify the full path.

[basex-talk] JSON serialization/compatibility with exist-db JSON?

2019-01-02 Thread Andreas Jung
Hi there, I have an issue with the migration of an XQuery script from eXist to Basex: The link https://gist.github.com/zopyx/467a01264d53bdaa48ad27cd553cfda8 shows the script and the expected (status quo) output for XML and JSON. Calling the script using /rest/foo/?run=foo.xql=json