Changes

Jump to navigation Jump to search
267 bytes added ,  17:14, 26 October 2017
no edit summary
==Conversion Formats==
 
'''A little advice''': in the Database Creation dialog of the GUI, if you select JSON Parsing and switch to the ''Parsing'' tab, you can see the effects of some of the conversion options.
===Direct===
** The existing types are ''string'', ''number'', ''boolean'', ''null'', ''object'', and ''array''.
** As most values are strings, the ''string'' type is by default omitted.
 
===XQuery===
 
The {{Code|xquery}} format is lossless, too. It converts a JSON document to an XQuery map and vice versa. The conversion rules are the same as for [[XQuery 3.1#fn:parse-json|fn:parse-json]]. Before {{Version|9.0}}, it was named {{Code|map}} (it has been renamed because it may also generate strings and other types).
===Basic===
The {{Code|jsonml}} format is designed to convert XML to JSON and back, using the JsonML dialect. JsonML allows the transformation of arbitrary XML documents, but namespaces, comments and processing instructions will be discarded in the transformation process. More details are found in the official [http://jsonml.org/XML JsonML documentation].
'''A little advice''': in the Database Creation dialog of the GUI===XQuery=== The {{Code|xquery}} format is lossless, if you select too. It converts a JSON Parsing document to an XQuery value and switch to vice versa. The conversion rules are the ''Parsing'' tabsame as for [[XQuery 3.1#fn:parse-json|fn:parse-json]]. The resulting representation will consume less memory than XML-based formats, you and values can see be directly accessed without conversion. Thus, it is recommendable for very large inputs and for efficient ad-hoc processing. Before {{Version|9.0}}, the effects of some of format was called {{Code|map}} (it has been renamed because the conversion optionsresulting value may also be a string, number, boolean, or an empty sequence).
==Options==
Bureaucrats, editor, reviewer, Administrators
13,550

edits

Navigation menu