Changes

It presents different the available parsers for importing that can be used to import various datasource into sources in BaseX databases. For export see Please visit the [[Serialization]]article if you want to know how to export data.

==XML Parsers==

BaseX provides two parsers to import alternatives for parsing XML data:

* By default, the Java’s [http://download.oracle.com/javase/6/docs/api/javax/xml/parsers/SAXParser.html SAXParser] is used to parse XML documents.* The internal, built-in XML parser is used, which is more fault-tolerant than Java’s XML parser. It supports standard HTML entities out-of-the-box, and it is faster than the default parser, in most casesparticular if small documents are to be parsed. In turnHowever, it the internal parser does not support all oddities specified by DTDs, the full range of DTD features and cannot resolve [[Catalog_Resolver|catalogs]].* Java’s [http://download.oracle.com/javase/6/docs/api/javax/xml/parsers/SAXParser.html SAXParser] can also be selected for parsing XML documents. This parser is stricter than the built-in parser, but it refuses to process some large documents.

===GUI===

===Command Line===

To turn the internal XML parser and DTD parsing on/off, modfify modify the <code>INTPARSE</code> and <code>DTD</code> options:

SET [[Options#INTPARSE{{Option|INTPARSE]] }} true SET [[Options#DTD{{Option|DTD]] }} true

===XQuery===

The [[Database Module#db:add|db:add()]] or and [[Database Module#db:replace|db:replace()]]function functions can also be used as well to add new XML documents to the database.The following example query uses the internal XML parser and adds all filesto the database <code>DB</code> that are found in the directory<code>2Bimported</code>:

return db:add('DB', $file, '', map { 'intparse': true() })

==HTML Parser==

With If [http://homevrici.ccillojban.org/~cowan/XML/tagsoup/ TagSoup] is found in the [[Startup#Distributions|classpath]], HTML can be imported in BaseX without any problems. TagSoup ensures that only well-formed HTML arrives at the XML parser (correct opening and closing tags, etc.). Hence, if TagSoup is not available on a system, there will be a lot of cases where importing HTML fails, no matter whether you use the GUI or the standalone mode.

==Installation== ====Downloads=====

=====Maven=====

An easy way to add TagSoup to your own project is to follow this steps:

3. you can see on the first tab called Maven a , you can see an XML snippet like this :

<pre class="brush:xml"><dependency> <groupId>org.ccil.cowan.tagsoup</groupId> <artifactId>tagsoup</artifactId> <version>1.2.1</version> </dependency></pre>

4. copy that in your own maven project's project’s <code>pom.xml under </code> file into the <code><dependencies> tag</code> element.

5. don't don’t forget to run <code>mvn jetty:run</code> again

=====Debian=====

===TagSoup Options===

please visit the [http://homevrici.ccillojban.org/~cowan/XML/tagsoup/#program TagSoup] website. BaseX supports

* '''encoding''': BaseX tries to guess the input encoding , but this can be overwritten by the user if necessarythis option.

SET [[Options#PARSER{{Option|PARSER]] }} html SET [[Options#HTMLOPT{{Option|HTMLOPT]] HTMLPARSER}} method=xml,nons=true,ncdatanocdata=true,nodefaults=true,nobogons=true,nocolons=true,ignorable=true SET [[Options#CREATEFILTER{{Option|CREATEFILTER]] }} *.html

HTML files Documents can also be converted by specifying the HTML parser in the query prologand additional optionsas function arguments:

declare option dbfetch:parser xml("index.html";, map { 'parser': 'html',declare option db 'htmlparser':htmlopt "map { 'html=': false";(), 'nodefaults': true() }doc("index.html"})

==JSON Parser==

===GUI===

===Command Line===

SET [[Options#PARSER{{Option|PARSER]] }} json SET [[Options#PARSEROPT{{Option|PARSEROPT]] JSONPARSER}} encoding=utf-8, jsonml=true SET {{Option|CREATEFILTER}} *.json ==XQuery== The [[Options#CREATEFILTER|CREATEFILTERJSON Module]] *provides functions for converting JSON objects to XML documents.json

==CSV Parser==

===GUI===

===Command Line===

SET [[Options#PARSER{{Option|PARSER]] }} csv SET [[Options#PARSEROPT{{Option|PARSEROPT]] CSVPARSER}} encoding=utf-8, lines=true, header=false, separator=space SET [[Options#CREATEFILTER{{Option|CREATEFILTER]] }} *.csv

===XQuery=== The [[CSV Module]] provides a function for converting CSV to XML documents.

The CSV parser Documents can also be specified converted by specifying the parser in the prolog of an XQuery expression.The [[Database Module#db:add|db:add()]] or [[Database Module#db:replace|db:replace()]]function can be used to add the specified source files into the database.The following example query adds all CSV files to the database <code>DB</code>that are found located in the directory <code>{{Code|2Bimported</code>, }} to the database {{Code|DB}} and interprets thefirst lines as column headers:

return db:add('"DB'", $file, "", map { 'parser': 'csv', 'csvparser': map { 'header': true() }})

==Text Parser==

===GUI===

===Command Line===

SET [[Options#PARSER{{Option|PARSER]] }} text SET [[Options#PARSEROPT{{Option|PARSEROPT]] TEXTPARSER}} lines=yes SET [[Options#CREATEFILTER{{Option|CREATEFILTER]] }} *

===XQuery===

AgainSimilar to the other formats, the text parser can also be specified in the prolog of an via XQuery expression, andthe [[Database Module#db:add|db:add()]] or [[Database Module#db:replace|db:replace()]]function can be used to add the specified source files into the database.The following example query adds all text files to the database <code>DB</code>that are found in the directory <code>2Bimported</code> and its sub-directories:

return db:add('"DB'", $file, "", map { 'parser': 'text' })

* Removed: CSV option "format".

* Updated: the CSV {{Code|SEPARATOR }} option of CSV parser may now contain be assigned arbitrary code points.single characters

* Updated: Enhanced support for TagSoup options. [[Category: Beginner]]