Re: [basex-talk] xquery result limit

As I overlooked in your last example, you did not use 'order by'. Without sorting, only the number of requested results will be created, no matter if you use the GUI or work on command-line. The most prominent example of this is the following query (which would be extremely slow and memory

Re: [basex-talk] xquery result limit

On Fri, 2016-11-11 at 19:01 +0200, George Sofianos wrote: > So If I get it right, when I use [position() = 1 to 100], only the > first 100 results are calculated? or all 900.000 rows are calculated, > and I get the first 100 results? (imagine it is a complex query) Note that an order by clause

Re: [basex-talk] xquery result limit

> So If I get it right, when I use [position() = 1 to 100], only the first 100 > results are calculated? or all 900.000 rows are calculated, and I get the > first 100 results? (imagine it is a complex query) All elements will be created, but only the first 100 will need to be cached in the GUI.

Re: [basex-talk] xquery result limit

No problem! I am just asking because large results in the query will first be cached before they are displayed in the GUI. On command-line, single items will be iteratively output as soon as possible. As a consequence, outputting zour 900,000 rows shouldn’t cause additional overhead on

Re: [basex-talk] xquery result limit

> I'm testing the scripts on GUI, I don't really use command line. I also run > them on a basexhttp instance. > I will check it out, however I like to keep the scripts as close to the > xquery spec as possible. No problem! I am just asking because large results in the query will first be cached

Re: [basex-talk] Exporting large table from RDBMS

Thanks! This looks like a blocker: > { > $sql-results ! > > {./sql:column[lower-case(@name)="id"]/string()} > {./sql:column[lower-case(@name)="name"]/string()} > {./sql:column[lower-case(@name)="timestamp"]/string()} > {./sql:column[lower-case(@name)="value"]/string()} >

Re: [basex-talk] xquery result limit

Do you run the query in the GUI or on command-line? For even better performance, I recommend you to have a look at the following HOF function: http://docs.basex.org/wiki/Hof_Module#hof:top-k-by I'm testing the scripts on GUI, I don't really use command line. I also run them on a

Re: [basex-talk] xquery result limit

> Hi, thanks for quick reply. I'm more interested on the memory consumption > and execution speed. I have a result of about 90 rows and it looks like > limiting the result like that also helps on the performance aspect. But I'm > not sure about that. Is the whole result saved in memory then

Re: [basex-talk] Exporting large table from RDBMS

Hi Christian, as usual thanks for the attention. I send you the query [1], the transformation function [2] and the stacktrace [4]. Database is MySQL 5.7.13 with jdbc driver mysql-connector-java-5.1.39-bin.jar. Everything deployed on a single host running win7 32 bit. Thanks again! Marco. [1]

Re: [basex-talk] xquery result limit

> Hi, I've found this very good answer to limiting results in xquery. > http://stackoverflow.com/a/8900472/1951487 > I like that it works, but I was wondering if you can explain what happens in > the background? Hm… What do you want to know exactly? ;) What does our query processor? How does

[basex-talk] xquery result limit

Hi, I've found this very good answer to limiting results in xquery. http://stackoverflow.com/a/8900472/1951487 I like that it works, but I was wondering if you can explain what happens in the background? Thanks, George

Re: [basex-talk] Exporting large table from RDBMS

…more input would be welcome ;) > Marco, I've faced the same problem and frustration, and I agree that it > would be great if BaseX could be used for such tasks. Strengthening its > potential role as a data integration engine. > Kind regards, > Hans > > > Marco Lettere

Re: [basex-talk] Exporting large table from RDBMS

Marco, I've faced the same problem and frustration, and I agree that it would be great if BaseX could be used for such tasks. Strengthening its potential role as a data integration engine.Kind regards,Hans Marco Lettere schrieb am 10:57 Freitag, 11.November 2016:

Re: [basex-talk] Exporting large table from RDBMS

Hi Marco, Generally, the BaseX SQL Module is capable of streaming results. It is usually up to the corresponding SQL Java driver how large result sets are handled. Maybe you can provide us with the Java stack trace; it could help finding the culprit. Cheers, Christian On Fri, Nov 11, 2016 at

Re: [basex-talk] expath-pkg.xml on the server-side not recognized

Hm. Some more information would help ;) Cold you prepare an MCVE? On Fri, Nov 11, 2016 at 2:15 PM, Rob Stapper wrote: > Hi, > > > > It’s been a while. Doing other stuff. But in my spare time I’m still using > Basex. > > > > I’m fiddling around with client-server concepts

[basex-talk] expath-pkg.xml on the server-side not recognized

Hi, It's been a while. Doing other stuff. But in my spare time I'm still using Basex. I'm fiddling around with client-server concepts over http and I find that on the server-side, the expath-pkg.xml is ignored. Modules in repo can't be addressed by means of expath-pkg. I wonder if this

[basex-talk] Exporting large table from RDBMS

Hi all, I'm currently facing the issue of exporting a large table stored in a MySQL instance to a csv that has then to be zipped and served through a web service. I'd love to use XQuery and the Basex functionality for doing it because it feels perfectly natural. The problem is that the