BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

Fwd: basex_7.5-1_amd64.changes ACCEPTED into unstable
by Alexander Holupirek 17 Jan '13

17 Jan '13

To all the Debian users. BaseX 7.5 has been accepted in unstable. Sorry for letting you wait so long. Begin forwarded message: > From: Debian FTP Masters <ftpmaster(a)ftp-master.debian.org> > Subject: basex_7.5-1_amd64.changes ACCEPTED into unstable > Date: 18. Januar 2013 00:17:33 MEZ > To: Alexander Holupirek <alex(a)holupirek.de>, <tmancill(a)debian.org> > > Accepted: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Format: 1.8 > Date: Tue, 15 Jan 2013 10:00:12 +0100 > Source: basex > Binary: basex > Architecture: source all > Version: 7.5-1 > Distribution: unstable > Urgency: low > Maintainer: Alexander Holupirek <alex(a)holupirek.de> > Changed-By: Alexander Holupirek <alex(a)holupirek.de> > Description: > basex - XML database and XPath/XQuery processor > Closes: 696796 696804 697037 > Changes: > basex (7.5-1) unstable; urgency=low > . > * New upstream release (December 21, 2012) (closes: #697037) > XQUERY UPDATE > - bulk updates are now much faster than before > - insert and replace operations take much less memory > - databases can now be created via XQuery and db:create() > . > GUI TEXT EDITOR > - a fast and flexible search/replace panel has been added > - error highlighting has been extended to XML files > - the editor was improved for editing arbitrary text files > . > XQUERY 3.0 > - the code has been aligned with latest changes in the specs > - HTML5 support has been updated > . > WEB APPLICATIONS > - new modules have been added: Request, Session, Sessions > - logging has been revised and extended to HTTP requests > - SSL support added, switched to Jetty 8 > - all operation modes have been unified and simplified > - RESTXQ elements added to simplify forwarding and redirects > . > CORE FEATURES > - improved stability of concurrent read/write operations > - the INSPECT command performs database sanity checks > - EXECUTE triggers the execution of command scripts > . > * Packaging: > - Added example provided by jidanni(a)jidanni.org to basex.1 > Thanks! (closes: #696804) > - Added note for missing -q option to basex.1 (closes: #696796) > Reported issue upstream: > https://github.com/BaseXdb/basex/issues/620 > Checksums-Sha1: > f2557eb167c7833402ce771a1fb8b1bd7499a0a8 1856 basex_7.5-1.dsc > 9dd929c365333bc6bcc2681b782c4fcaaad3a94a 1315007 basex_7.5.orig.tar.gz > e8b7ff70d349bf4b69b588b74aa69f2b82dbb016 98461 basex_7.5-1.debian.tar.gz > 2e9f5a817befb3a680822cb58ad808f42e98c461 2489490 basex_7.5-1_all.deb > Checksums-Sha256: > 017ecab180dda4499b557f537f7f30813a7b615af47dc8d8bae827d02f47fe3d 1856 basex_7.5-1.dsc > 3fbc7b2fe2aa7427ad312cbe0aded3fcc86d029e6f6cd38476c5fc5d59ef7c30 1315007 basex_7.5.orig.tar.gz > 851bd420ecc0e9ac706a80251b7dd7ffbc9adec7cd83ecc99173a00705f26494 98461 basex_7.5-1.debian.tar.gz > 211f97595d0004e71ae2cd9d3822e13e54eb111b37a5ec25362d8ec9d0dfc315 2489490 basex_7.5-1_all.deb > Files: > 0a815272fac2cf303c9fce8350faace9 1856 database optional basex_7.5-1.dsc > 7028a0e81cecf02b73ba6d30cdc261fd 1315007 database optional basex_7.5.orig.tar.gz > a6b8dc8d172e8cfa93af05c18644b390 98461 database optional basex_7.5-1.debian.tar.gz > 3b3571e5b6d078867e40329bfc06ffb3 2489490 database optional basex_7.5-1_all.deb > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > > iQIcBAEBAgAGBQJQ+IDGAAoJECHSBYmXSz6WT4IP/1tKOwPKJlzDQGHrDZM015vD > OFo300qJK32pSD9HDHfKBpp8m6+DqpgEzzE7xeCbo2/o/1r6y8JZHGbgNxIw+AhB > Vio2fcq7EYelj2/NEGaohAhMsCVqpwxGdAcO+WURjJZJUBphO7dZxv8uFDY2d/yD > 9NRLm4Ta63c9Whg5ozMaWh3KNJR/fc6AksPH1rMgKqWETJvnm5VgLuEYV2pd/+x4 > fH6QeDxeko1GGQZUaXQjf+bqWff+QRaCevy6rQOkF6Io/PYOfniuhBGIMEm4fs/d > +SGc8dGuXOgaJ2ALeb6yG0ZnMdeEVQ9vRO5LcJJv+YkMmIG75LewojXMpwwFGA/J > Af4o6WS4zFjHH+dLAbsKntrDhiLd1h3T8Urt9CA3T3cEP4xTUWDjNRAEwV5ebqRG > veD7qPzLXZErVKcrLKXaYXEg5sYS0DIjB0Q6sUYYPDfUmhYTIFTyRf3vaDuoc0Er > xW24/we8aVAnSAOcg63dPKajUz+slnxZPn6iNgqJUe+r1R1Qn/aMntPZfgeARmmx > YZKN5GXcABzCPx7N+LGyXTOPg4fkda+vFK8x70vm2Sf0Tet0Z4PBPvxKDMQzu9BF > H/7tHLAqM8aCWZNfHz8e12xbQctyaZiz6i24i9F1a+Dh94Vjjpvyd7HBZ7ZcHWnb > jo6iobCXljlk20aa/JlO > =/S7U > -----END PGP SIGNATURE----- > > > Thank you for your contribution to Debian.

1 0

Changing content through Data Source/Oxygen
by France Baril 17 Jan '13

17 Jan '13

Hi, Our .xqm uses a configuration file that is stored in a DB called AppResources. When we use the GUI to create/upload the content for AppResources, we can access our restxq pages and the result is based on our config. If we access the config file in Oxygen and change anything, even a space, it's like the .xqm cannot access the information anymore. We tried: - Updating/optimize the index/paths. - Stopping/starting the server. The file is saved properly. If we save it on disk from Oxygen and reload AppResources with the config file, we are able to access the information in the file again. So the issue is really the fact that the change occurs through webdav. What are we missing here? Regards, France -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

2 11

fastest way to add/replace/delete xml
by Fabrice Etanchaud 17 Jan '13

17 Jan '13

Dear all, I have to store and replace xml pieces, and am wondering what can be the fastest way to achieve that task. - Add provided files containing several xml pieces, and then use xquery update to replace nodes ? - Or split files to add a document per xml piece, and then use db:replace ? These databases have size near the physical limit. Regards, Fabrice Etanchaud Questel-Orbit

2 1

[XQuery] Sharing a value between expressions?
by Johannes Krampf 16 Jan '13

16 Jan '13

Hello, I would like to assign a sequence to a variable and then share this variable between two expressions. Particularly I want to create a list of documents to delete from the db and then return the number of deleted documents. Code sketch of what I am trying: let $nodes := [...] let $base-uris := for $node in $nodes return base-uri($node) let $distinct-base-uris := distinct-values($base-uris) for $base-uri in $distinct-base-uris return db:delete("db", $base-uri), return count($distinct-base-uris) --- The problem with this approach is that $distinct-base-uris is local to the first expressions and not in scope for the count call. I tried to just duplicate all code, but then I get an error message that "no updating expression [is] allowed". Is there any way to achieve what I want and put my value in a scope accessible by both expressions? Regards, Johannes

2 2

DB freezes on updating restxq - a simpler example
by France Baril 15 Jan '13

15 Jan '13

Hi, I have sent a request for this issue last month, but my example was too complex. Here is the simplest example I could get that reproduces the issue. This seems to be a problem with updating restqx functions, so I'm unsure how to reproduce it with a .bsx. If you use the attached db with the attached query on localhost:8984. The browser should freeze on BaseXMas when accessing debug/debug-freeze. - The xslt works. If you make the function none updating and return $result. You'll see the video.png in the browser. - The updating function works. If you replace the node $result with <hey/> and comment out the xslt:transform line. The document will be replace in the db. - The two don't work together. Specific characteristic if this xsl: - It uses a rest access to extract the path for the video. Without the doc('http://...rest…') line, this would work. Note that this used to work with prior versions of BaseX. Thanks, France -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

2 1

Database locking pre-release published
by Jens Erat 15 Jan '13

15 Jan '13

Dear BaseX community, we're glad to announce some pre-release-version of a much-requested and long-awaited feature: database locking. Database locking will enable higher parallelism, it will be possibly to perform updates to some database without blocking all other databases (actually even parallel updates to different databases). Please notice this is a pre-release developer version which is not yet fully tested and optimized. We will announce as soon as we regard it ready for production. It is included in most current [development release]. Have a look at our [wiki documentation] for more information on limitations and [how to enable]. During the next weeks, we will continue to include more optimizations and reduce the number of queries requiring global locks and add fixes if necessary. We will be glad receiving your feedback! As I'll be writing my thesis on these locking enhancements, I'd also be glad on some user stories and requirements (which could be considered in prioritizing efforts on optimizations, too). You can also mail me directly if you do not want to post to the list. Regards from Lake Constance, Germany, Jens Erat [development release]: http://files.basex.org/releases/latest/ [wiki documentation]: http://docs.basex.org/wiki/Transaction_Management [how to enable]: http://docs.basex.org/wiki/Transaction_Management#How_to_enable -- Jens Erat [phone]: tel:+49-151-56961126 [mail]: mailto:email@jenserat.de [jabber]: xmpp:jabber@jenserat.de [web]: http://www.jenserat.de PGP: 350E D9B6 9ADC 2DED F5F2 8549 CBC2 613C D745 722B

1 0

Determining whether a function exists
by Charles Duffy 15 Jan '13

15 Jan '13

Howdy -- I'm trying to determine whether sql:execute-prepared exists, to have a module that functions in both BaseX 7.3 and 7.5. However -- exists(function-lookup(xs:QName("sql:execute-prepared"), 2)) returns false even in BaseX 7.5, even though function-name(function-lookup(xs:QName("sql:execute-prepared"), 2)) properly returns "sql:execute-prepared". Am I going to have to use a try block to detect this case?

2 3

256 namespaces limit
by Imsieke, Gerrit, le-tex 15 Jan '13

15 Jan '13

Dear Team, Do you plan on increasing the 256 namespaces limit any time soon? I know that there is the STRIPNS option, but this does not fit my use case (which is to index all my XSLT and XProc files) too well. Gerrit

3 2

unzip
by Jason Harrop 14 Jan '13

14 Jan '13

Hello eXist and MarkLogic both have mechanisms for unzipping a resource when it is loaded into the database. In eXist, you can use a trigger and its unzip module. For MarkLogic, you can use its Office OpenXML Extract pipeline. See http://robotbeerbash.wordpress.com/2009/08/31/getting-started-with-open-xml… What's the easiest way to do this sort of thing in basex? thanks .. Jason

4 7

Re: [basex-talk] best way to partition large data sets among collections
by pw＠themail.co.uk 14 Jan '13

14 Jan '13

Hi Christian Thank you for directing me to the profiling module, I think that is just what I need Cheers Peter > > > >---- Original Message ---- >From: christian.gruen(a)gmail.com >To: pw(a)themail.co.uk >Subject: Re: [basex-talk] best way to partition large data sets among >collections >Date: Mon, 14 Jan 2013 19:13:12 +0100 > >>Hi Peter, >> >>> Do you have any information to guide me here; what sorts of XQuery >>> expressions should I match with large numbers of collections, and >>> which with small numbers of collections? >> >>hmm, there is no answer I get in mind that could give you general >>guidance here, as XQuery provides just too many possibilities for >>writing slow and fast queries. Its similar to the question how to >>write efficient Java, Perl of whatever.. To do get more information >on >>why your queries are not as fast as they ideally should be, you >could >>e.g... >> >> check in the InfoView/query info if the relevant index structures >are used >> use functions of the Profiling Module [1] to track down >bottlenecks >> use -Xmx get do low level profiling >> >>Next, you may pass us on snippets of your code that may, in your >>opinion, be subject to being optimized. >>Christian >> >>[1] http://docs.basex.org/wiki/Profiling_Module >> >> >>> If I am using data-rich XML there is a high ration of nodes to >>> content. What are the rules of thumb for this type of content? >>> >>> Are there any recommendations specifically for GML? >>> >>> Many thanks >>> >>> Peter >>> >>>> >>>> >>>> >>>>---- Original Message ---- >>>>From: christian.gruen(a)gmail.com >>>>To: pw(a)themail.co.uk >>>>Subject: Re: [basex-talk] best way to partition large data sets >among >>>>collections >>>>Date: Mon, 14 Jan 2013 13:05:00 +0100 >>>> >>>>>Hi Peter, >>>>> >>>>>thanks for the link. Theres no general answer for your question, >as >>>>>an application may both run flawlessly with a single or hundreds >of >>>>>databases, depending on how your XQuery expressions look like. If >>>>you >>>>>do regular updates, I suggest to split your data into fixed >>>>instances >>>>>that will never change, and use all indexes, and updating >instances >>>>>that may eventually be merged with the fixed instances if no more >>>>>changes are expected. >>>>> >>>>>Christian >>>>>___________________________ >>>>> >>>>>On Sun, Jan 13, 2013 at 1:09 AM, <pw(a)themail.co.uk> wrote: >>>>>> Hello List >>>>>> >>>>>> I am experimenting with statistical data ( >>>>>> http://www.semantechs.co.uk/ ) and found that organising 2.5Gb >of >>>>xml >>>>>> data into 12 unevenly sized collections ranging from 40 to >400Mb >>>>>> performs much more slowly than 36 collections each containing >>>>>> approximately 75Mb of data. >>>>>> >>>>>> What rules of thumb are there to guide me in designing the most >>>>>> performant database? >>>>>> >>>>>> Many thanks >>>>>> >>>>>> Peter >>>>>> >>>>>> _______________________________________________ >>>>>> BaseX-Talk mailing list >>>>>> BaseX-Talk(a)mailman.uni-konstanz.de >>>>>> https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk >>>>> >>> >>> >>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk