Changes

Jump to navigation Jump to search
997 bytes removed ,  13:31, 2 July 2020
=Conventions=
All functions and errors in this module are assigned to the <code><nowiki>http://basex.org/modules/sql</nowiki></code> namespace, which is statically bound to the {{Code|sql}} prefix.<br/>All errors are assigned to the <code><nowiki>http://basex.org/errors</nowiki></code> namespace, which is statically bound to the {{Code|bxerr}} prefix.
=Functions=
|-
| '''Errors'''
|{{Error|BXSQ0007init|XQuery Errors#SQL Functions Errors}} the specified driver class is not found.
|}
|-
| width='120' | '''Signatures'''
|{{Func|sql:connect|$url as xs:string|xs:integeranyURI}}<br/ >{{Func|sql:connect|$url as xs:string, $user as xs:string, $password as xs:string|xs:integeranyURI}}<br/ >{{Func|sql:connect|$url as xs:string, $user as xs:string, $password as xs:string, $options as map(xs:string, item()*)?|xs:integeranyURI}}<br/ >
|-
| '''Summary'''
|This function establishes a connection to a relational database. As a result and returns a connection handle is returnedid. The parameter {{Code|$url}} is the URL of the database and shall be of the form: {{Code|jdbc:<driver name>:[//<server>[/<database>]]}}. If the parameters {{Code|$user}} and {{Code|$password}} are specified, they are used as credentials for connecting to the database. The {{Code|$options}} parameter can be used to set connection options.
|-
| '''Errors'''
|{{Error|BXSQ0001error|XQuery Errors#SQL Functions Errors}} an SQL exception occurs, e.g. missing JDBC driver or not existing relationoccurred when connecting to the database.
|-
| '''Examples'''
|Connects to an SQL Server and sets autocommit to {{Code|true}}:
<pre classsyntaxhighlight lang="brush:xquery">
sql:connect('dbc:sqlserver://DBServer', map { 'autocommit': true() })
</presyntaxhighlight>
|}
==sql:execute==
 
{{Mark|Updated with Version 8.7}}: Return update count for updating statements.
 
Once a connection is established, the returned connection handle can be used to execute queries on the database. Our SQL module supports both direct queries and prepared statements.
{| width='100%'
|-
| width='120' | '''Signatures'''
|{{Func|sql:execute|$connection id as xs:integeranyURI, $query statement as xs:string|item()*}}<br/>{{Func|sql:execute|$id as xs:anyURI, $statement as xs:string, $options as map(*)?|item()*}}
|-
| '''Summary'''
| This function executes a query or update statement. The parameter an SQL {{Code|$connectionstatement}} specifies a , using the connection handle. The parameter with the specified {{Code|$queryid}} is a string representing an SQL statement. The returned result depends on the kind of statement:* If the result is updatingan update statement was executed, the number of updated rows will be returned as integer.
* Otherwise, an XML representation of all results will be returned.
With {{Code|$options}}, the following parameter can be set:
* {{Code|timeout}}: query execution will be interrupted after the specified number of seconds.
|-
| '''Errors'''
|{{Error|BXSQ0001error|XQuery Errors#SQL Functions Errors}} an error occurred while executing SQL exception occurs, e.g. <br/ >{{Error|id|#Errors}} the specified connection does not existing relation is retrievedexist.<br/ >{{Error|BXSQ0002timeout|XQuery Errors#SQL Functions Errors}} a wrong connection handle is passedquery execution exceeded timeout.<br/ >
|}
==sql:execute-prepared==
 
{{Mark|Updated with Version 8.7}}: Return update count for updating statements.
{| width='100%'
|-
| width='120' | '''Signatures'''
|{{Func|sql:execute-prepared|$id as xs:integeranyURI, $params as element(sql:parameters)|item()*}}<br/>{{Func|sql:execute-prepared|$id as xs:anyURI, $params as element(sql:parameters), $options as map(*)?|item()*}}
|-
| '''Summary'''
| This function executes a prepared statement:* with the specified {{Code|$id}}. The output format is identical to [[#sql:execute|sql:execute]].* The parameter {{Code|$id}} specifies a prepared statement handle.* The optional parameter {{Code|$params}} is an element {{Code|<sql:parameters/>}} representing the parameters for a prepared statement along with their types and values. The following schema shall be used:<br/ ><pre classsyntaxhighlight lang="brush:xmlxquery">
element sql:parameters {
element sql:parameter {
attribute type { "int" | "string" | "boolean" | "date" | "double" |
"float" | "short" | "time" | "timestamp" | "sqlxml" },
attribute null { "true" | "false" }?,
text
}+
}?
</presyntaxhighlight>With {{Code|$options}}, the following parameter can be set:* {{Code|timeout}}: query execution will be interrupted after the specified number of seconds.
|-
| '''Errors'''
|{{Error|BXSQ0001attribute|XQuery Errors#SQL Functions Errors}} an SQL exception occurs, e.g. not existing relation is retrieved.<br/ >attribute different from {{ErrorCode|BXSQ0002|XQuery Errors#SQL Functions Errorstype}} a wrong prepared statement handle is passed.<br/ >and {{ErrorCode|BXSQ0003|XQuery Errors#SQL Functions Errorsnull}} the number of is set for a {{Code|<sql:parameter/>}} elements in element.<br/ >{{CodeError|error|<sql:parameters/>#Errors}} differs from the number of placeholders in the prepared statementan error occurred while executing SQL.<br/ >{{Error|BXSQ0004id|XQuery Errors#SQL Functions Errors}} the type of a parameter for a prepared statement is specified connection does not specifiedexist.<br/ >{{Error|BXSQ0005parameters|XQuery Errors#SQL Functions Errors}} an attribute different from {{Code|no parameter type}} and specified.<br/>{{CodeError|null}} is set for a {{Codetimeout|<sql:parameter/>#Errors}} elementquery execution exceeded timeout.<br/ >{{Error|BXSQ0006type|XQuery Errors#SQL Functions Errors}} the value of a parameter is from type date, time or timestamp and its value is in an invalid cannot be converted to the specified format.<br/ >
|}
|-
| width='120' | '''Signatures'''
|{{Func|sql:prepare|$connection id as xs:integeranyURI, $statement as xs:string|xs:integeranyURI}}
|-
| '''Summary'''
|This function prepares a statement and returns a handle to it. The parameter an SQL {{Code|$connectionstatement}} indicates , using the specified connection handle to be used. The parameter {{Code|$statementid}} , and returns the id reference to this statement. The statement is a string representing an SQL statement with one or more '?' placeholders. If the value of a field has to be set to {{Code|NULL}}, then the attribute {{Code|null}} of the element {{Code|<sql:parameter/>}} has to element must be {{Code|true}}.
|-
| '''Errors'''
|{{Error|BXSQ0001error|XQuery Errors#SQL Functions Errors}} an error occurred while executing SQL exception occurs.<br/ >{{Error|BXSQ0002id|XQuery Errors#SQL Functions Errors}} a wrong the specified connection handle is passeddoes not exist.<br/ >
|}
|-
| width='120' | '''Signatures'''
|{{Func|sql:commit|$connection id as xs:integeranyURI|empty-sequence()}}
|-
| '''Summary'''
| This function commits the changes made to a relational database. , using the specified connection {{Code|$connectionid}} specifies the connection handle.
|-
| '''Errors'''
|{{Error|BXSQ0001error|XQuery Errors#SQL Functions Errors}} an error occurred while executing SQL exception occurs.<br/ >{{Error|BXSQ0002id|XQuery Errors#SQL Functions Errors}} a wrong the specified connection handle is passeddoes not exist.<br/ >
|}
|-
| width='120' | '''Signatures'''
|{{Func|sql:rollback|$connection id as xs:integeranyURI|empty-sequence()}}
|-
| '''Summary'''
| This function rolls back the changes made to a relational database. , using the specified connection {{Code|$connectionid}} specifies the connection handle.
|-
| '''Errors'''
|{{Error|BXSQ0001error|XQuery Errors#SQL Functions Errors}} an error occurred while executing SQL exception occurs.<br/ >{{Error|BXSQ0002id|XQuery Errors#SQL Functions Errors}} a wrong the specified connection handle is passeddoes not exist.<br/ >
|}
|-
| width='120' | '''Signatures'''
|{{Func|sql:close|$connection id as xs:integeranyURI|empty-sequence()}}
|-
| '''Summary'''
| This function closes a database connection to a relational database. with the specified {{Code|$connectionid}} specifies the connection handle.<br/>Opened connections will automatically be closed after the XQuery expression has been evaluated, but in order to save memory, it is always recommendable to explicitly close them with this function if you open many connectionsthat are not used anymore.
|-
| '''Errors'''
|{{Error|BXSQ0001error|XQuery Errors#SQL Functions Errors}} an error occurred while executing SQL exception occurs.<br/ >{{Error|BXSQ0002id|XQuery Errors#SQL Functions Errors}} a wrong the specified connection handle is passeddoes not exist.<br/ >
|}
A simple select statement can be executed as follows:
<pre classsyntaxhighlight lang="brush:xquery">let $conn id := sql:connect("jdbc:postgresql://localhost:5432/coffeehouse")return sql:execute($connid, "SELECT * FROM coffees WHERE price < 10")</presyntaxhighlight>
The result may look like:
<pre classsyntaxhighlight lang="brush:xml">
<sql:row xmlns:sql="http://basex.org/modules/sql">
<sql:column name="cof_name">French_Roast</sql:column>
<sql:column name="total">14</sql:column>
</sql:row>
</presyntaxhighlight>
==Prepared Statements==
A prepared select statement can be executed in the following way:
<pre classsyntaxhighlight lang="brush:xquery">
(: Establish a connection :)
let $conn := sql:connect("jdbc:postgresql://localhost:5432/coffeehouse")
(: Execute prepared statement :)
return sql:execute-prepared($prep, $params)
</presyntaxhighlight>
==SQLite==
The following expression demonstrates how SQLite can be addressed using with the [httphttps://bitbucket.org/xerial/sqlite-jdbc / Xerial SQLite JDBC driver]:
<pre classsyntaxhighlight lang="brush:xquery">
(: Initialize driver :)
sql:init("org.sqlite.JDBC"),
sql:execute($conn, "select * from person")
)
</presyntaxhighlight>
=Errors=
|Description
|-
|{{Code|BXSQ0001attribute}}|An SQL exception occurred (e.g.attribute different from {{Code|type}} and {{Code|null}} is set for a {{Code|&lt;sql: a non-existing relation is retrieved)parameter/&gt;}} element.
|-
|{{Code|BXSQ0002error}}|A wrong connection handle or prepared statement handle is passedAn SQL exception occurred.
|-
|{{Code|BXSQ0003id}}|The number of {{Code|&lt;sql:parameter/&gt;}} elements in {{Code|&lt;sql:parameters/&gt;}} differs from the number of placeholders in the prepared statementA connection does not exist.
|-
|{{Code|BXSQ0004init}}|The type of a parameter for a prepared statement A database driver is not specifiedfound.
|-
|{{Code|BXSQ0005parameters}}|An attribute different from {{Code|No parameter type}} and {{Code|null}} is set for a {{Code|&lt;sql:parameter/&gt;}} elementspecified.
|-
|{{Code|BXSQ0006timeout}}|A parameter is from type date, time or timestamp and its value is in an invalid formatQuery execution exceeded timeout.
|-
|{{Code|BXSQ0007type}}|A The value of a parameter cannot be converted to the specified database driver class is not foundformat.
|}
=Changelog=
;Version 89.70 * Updated: [[#sql:execute|sql:execute]], [[#sql:execute-prepared|sql:execute-prepared]]: Return update count for updating statements.{{Code|$options}} argument added.* Updated: Connection ids are URIs now.* Updated: error codes updated; errors now use the module namespace
;Version 7.5
 
* Updated: prepared statements are now executed via [[#sql:execute-prepared|sql:execute-prepared]]
The module was introduced with Version 7.0.
Bureaucrats, editor, reviewer, Administrators
13,550

edits

Navigation menu