BaseX 10 - Revision history

CG: Text replacement - "syntaxhighlight" to "pre"

2023-12-01T16:39:35Z

Text replacement - "syntaxhighlight" to "pre"

CG: Text replacement - "" to "

2023-12-01T16:35:07Z

Text replacement - "<syntaxhighlight lang="xquery">" to "<pre lang='xquery'>"

CG: Text replacement - "" to ""

2023-12-01T16:31:39Z

Text replacement - "</syntaxhighlight>" to "</pre>"

CG: /* Whitespaces */

2023-08-09T10:20:44Z

Whitespaces

CG: /* Whitespaces */

2023-08-09T10:18:51Z

Whitespaces

CG: /* Whitespaces */

2023-08-09T10:17:48Z

Whitespaces

CG: /* Whitespaces */

2023-08-09T10:14:39Z

Whitespaces

CG: /* Whitespaces */

2023-08-09T10:14:24Z

Whitespaces

CG: /* Whitespaces */

2023-08-09T10:13:18Z

Whitespaces

Andy Bunce: Add note on boundary-space preserve

2023-07-05T15:42:40Z

Add note on boundary-space preserve

@@ Line 26: / Line 26: @@
 Please be warned that the new default can throw off existing applications. If you want to restore the old behavior, you should attach the following lines in your [[Configuration|.basex configuration file]]…
-<syntaxhighlight lang="php">
+<pre lang="php">
 # Local Options
 STRIPWS = true
@@ Line 317: / Line 317: @@
 Results in the {{Code|rest}} namespace are now returned without prefix:
-<syntaxhighlight lang="xml">
+<pre lang="xml">
 <!-- before -->
 <rest:databases xmlns:rest="http://basex.org/rest"/>

@@ Line 34: / Line 34: @@
 …or add context parameters in the {{Code|web.xml}} file of your [[Web Application]]:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 <context-param>
    <param-name>org.basex.stripws</param-name>
@@ Line 50: / Line 50: @@
 Note that {{Option|STRIPWS}} only applies to stored XML and not to XML constructed within XQuery source files. Within XQuery code, the standard {{Code|boundary-space}} setting applies. This defaults to {{Code|strip}}. To preserve XML whitespace in XQuery modules, add the following to the prolog:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 declare boundary-space preserve;
 <xml> </xml>
@@ Line 61: / Line 61: @@
 The new feature can e.g. be used to store maps in a database:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 db:put-value(
    'factbook',
@@ Line 74: / Line 74: @@
 …and use them as index later on:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 let $cities := db:get-value('factbook', 'cities')
 for $country in ('Japan', 'Indonesia', 'Malaysia')
@@ Line 105: / Line 105: @@
 Lock detection will be performed after the first step, and the code resulting from this step offers much more insight into which specific databases need to be locked. As a result, local locks can be applied to many more queries than before, and many queries can now run in parallel. An example:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 declare variable $n external;
 db:get('names-' || $n)
@@ Line 118: / Line 118: @@
 XQuery Update provides constructs to [[XQuery Update#Main-Memory Updates|update XML nodes in main memory]]. The data structures for in-memory representations of XML resources have been revised, such that updates can be performed orders of magnitudes faster than before. With BaseX 9.x, the following query runs for several minutes, whereas it can now be computed in a few seconds:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 <xml>{
    (1 to 1000000) ! <child/>
@@ Line 133: / Line 133: @@
 ; Store data:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 let $email := map:merge(
    for $address in db:get('addressbook')//address
@@ Line 143: / Line 143: @@
 ; Retrieve data:
-<syntaxhighlight lang="xquery">
+<pre lang='xquery'>
 let $name := 'Richard David James'
 return store:get('email')($name)

@@ Line 30: / Line 30: @@
 STRIPWS = true
 SERIALIZER = indent=yes
-</syntaxhighlight>
+</pre>
 …or add context parameters in the {{Code|web.xml}} file of your [[Web Application]]:
@@ Line 43: / Line 43: @@
    <param-value>indent=yes</param-value>
 </context-param>
-</syntaxhighlight>
+</pre>
 In the GUI editor, a [[Shortcuts#Editor Shortcuts|shortcut]] and an icon were added to switch result indentation on and off.
@@ Line 53: / Line 53: @@
 declare boundary-space preserve;
 <xml> </xml>
-</syntaxhighlight>
+</pre>
 ==Value Resources==
@@ Line 70: / Line 70: @@
    'cities'
+)
-</syntaxhighlight>
+</pre>
 …and use them as index later on:
@@ Line 78: / Line 78: @@
 for $country in ('Japan', 'Indonesia', 'Malaysia')
 return $country || ': ' || string-join($cities?($country), ', ')
-</syntaxhighlight>
+</pre>
 ==Backups==
@@ Line 108: / Line 108: @@
 declare variable $n external;
 db:get('names-' || $n)
-</syntaxhighlight>
+</pre>
 After the query has been parsed, a user-specific value (e.g., {{Code|123}}) will be bound to {{Code|$n}}. The variable will be inlined by the compiler, and the argument of {{Function||db:get}} will be pre-evaluated to {{Code|names123}}. It is then easy for the lock detector to collect the name of the database that needs to read-locked before the query is eventually executed.
@@ Line 125: / Line 125: @@
    return insert node text { $pos } into $child
+}
-</syntaxhighlight>
+</pre>
 ==Key-Value Store==
@@ Line 139: / Line 139: @@
+)
 return store:put('emails', $email)
-</syntaxhighlight>
+</pre>
 ; Retrieve data:
@@ Line 146: / Line 146: @@
 let $name := 'Richard David James'
 return store:get('email')($name)
-</syntaxhighlight>
+</pre>
 The store is persistent: Its contents are written to disk if BaseX is shut down, and retrieved again after a restart.
@@ Line 323: / Line 323: @@
 <!-- now -->
 <databases xmlns="http://basex.org/rest"/>
-</syntaxhighlight>
+</pre>
 When listing the resources of a database, {{Code|dir}} elements are returned for resources that are located in subdirectories. See [[REST]] for more details.

@@ Line 49: / Line 49: @@
 In addition, databases may considerably increase in size, as whitespaces used for indenting an XML document will be interpreted and stored as additional text nodes. If your XML resources are structured and have no [[Full-Text#Mixed Content|mixed content]], it is advisable to enable whitespaces stripping when importing them to a database.
-Note {{Option|STRIPWS}} only applies to stored XML and not to XML constructed within XQuery source files. Within XQuery sources the standard {{Code|boundary-space}} setting applies. This defaults to {{Code|strip}}. To preserve XML whitespace in XQuery source add the following to the prolog:
+Note that {{Option|STRIPWS}} only applies to stored XML and not to XML constructed within XQuery source files. Within XQuery code, the standard {{Code|boundary-space}} setting applies. This defaults to {{Code|strip}}. To preserve XML whitespace in XQuery modules, add the following to the prolog:
 <syntaxhighlight lang="xquery">
 declare boundary-space preserve;

@@ Line 26: / Line 26: @@
 Please be warned that the new default can throw off existing applications. If you want to restore the old behavior, you should attach the following lines in your [[Configuration|.basex configuration file]]…
-<syntaxhighlight lang="xquery">
+<syntaxhighlight lang="php">
 # Local Options
 STRIPWS = true

@@ Line 24: / Line 24: @@
 The notorious {{Code|CHOP}} option was removed to prevent conflicting behavior caused by earlier installations. It was replaced by a new {{Option|STRIPWS}} option, which defaults to {{Code|false}}. In addition, the new default of the [[Serialization|serialization parameter]] {{Code|indent}} is {{Code|no}}.
-Please be warned that the new default can throw off existing applications. If you want to restore the old behavior, you should assign the following values in your [[Configuration|.basex configuration file]]…
+Please be warned that the new default can throw off existing applications. If you want to restore the old behavior, you should attach the following lines in your [[Configuration|.basex configuration file]]…
 <syntaxhighlight lang="xquery">
 STRIPWS=true
 SERIALIZER=indent=yes

← Older revision		Revision as of 15:42, 5 July 2023
Line 35:		Line 35:
	In addition, databases may considerably increase in size, as whitespaces used for indenting an XML document will be interpreted and stored as additional text nodes. If your XML resources are structured and have no [[Full-Text#Mixed Content\|mixed content]], it is advisable to enable whitespaces stripping when importing them to a database.		In addition, databases may considerably increase in size, as whitespaces used for indenting an XML document will be interpreted and stored as additional text nodes. If your XML resources are structured and have no [[Full-Text#Mixed Content\|mixed content]], it is advisable to enable whitespaces stripping when importing them to a database.

		+	Note {{Option\|STRIPWS}} only applies to stored XML and not to XML constructed within XQuery source files. Within XQuery sources the standard {{Code\|boundary-space}} setting applies. This defaults to {{Code\|strip}}. To preserve XML whitespace in XQuery source add the following to the prolog:
		+	<syntaxhighlight lang="xquery">
		+	declare boundary-space preserve;
		+	</syntaxhighlight>
	==Value Resources==		==Value Resources==