Difference between revisions of "SQL Module"
Line 18: | Line 18: | ||
|- | |- | ||
| '''Errors''' | | '''Errors''' | ||
− | |<b>[[XQuery Errors#SQL Functions Errors| | + | |<b>[[XQuery Errors#SQL Functions Errors|BXSQ0007]]</b> is raised if the specified driver class is not found. |
|} | |} | ||
Line 34: | Line 34: | ||
|- | |- | ||
| '''Errors''' | | '''Errors''' | ||
− | |<b>[[XQuery Errors#SQL Functions Errors| | + | |<b>[[XQuery Errors#SQL Functions Errors|BXSQ0001]]</b> is raised if an SQL exception occurs, e.g. missing JDBC driver or not existing relation. |
|} | |} | ||
Line 56: | Line 56: | ||
|- | |- | ||
| '''Errors''' | | '''Errors''' | ||
− | |<b>[[XQuery Errors#SQL Functions Errors| | + | |<b>[[XQuery Errors#SQL Functions Errors|BXSQ0001]]</b> is raised if an SQL exception occurs, e.g. not existing relation is retrieved.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0002]]</b> is raised if a wrong connection handle or prepared statement handle is passed.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0003]]</b> is raised if the number of <code><sql:parameter/></code> elements in <code><sql:parameters/></code> differs from the number of placeholders in the prepared statement.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0004]]</b> is raised if the type of a parameter for a prepared statement is not specified.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0005]]</b> is raised if an attribute different from <code>type</code> and <code>null</code> is set for a <code><sql:parameter/></code> element.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0006]]</b> is raised if a parameter is from type date, time or timestamp and its value is in an invalid format.<br/ > |
|} | |} | ||
Line 74: | Line 74: | ||
|- | |- | ||
| '''Errors''' | | '''Errors''' | ||
− | |<b>[[XQuery Errors#SQL Functions Errors| | + | |<b>[[XQuery Errors#SQL Functions Errors|BXSQ0001]]</b> is raised if an SQL exception occurs.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0002]]</b> is raised if a wrong connection handle is passed.<br/ > |
|} | |} | ||
Line 88: | Line 88: | ||
|- | |- | ||
| '''Errors''' | | '''Errors''' | ||
− | |<b>[[XQuery Errors#SQL Functions Errors| | + | |<b>[[XQuery Errors#SQL Functions Errors|BXSQ0001]]</b> is raised if an SQL exception occurs.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0002]]</b> is raised if a wrong connection handle is passed.<br/ > |
|} | |} | ||
Line 102: | Line 102: | ||
|- | |- | ||
| '''Errors''' | | '''Errors''' | ||
− | |<b>[[XQuery Errors#SQL Functions Errors| | + | |<b>[[XQuery Errors#SQL Functions Errors|BXSQ0001]]</b> is raised if an SQL exception occurs.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0002]]</b> is raised if a wrong connection handle is passed.<br/ > |
|} | |} | ||
Line 116: | Line 116: | ||
|- | |- | ||
| '''Errors''' | | '''Errors''' | ||
− | |<b>[[XQuery Errors#SQL Functions Errors| | + | |<b>[[XQuery Errors#SQL Functions Errors|BXSQ0001]]</b> is raised if an SQL exception occurs.<br/ > |
− | <b>[[XQuery Errors#SQL Functions Errors| | + | <b>[[XQuery Errors#SQL Functions Errors|BXSQ0002]]</b> is raised if a wrong connection handle is passed.<br/ > |
|} | |} | ||
Line 173: | Line 173: | ||
return sql:execute($prep, $params) | return sql:execute($prep, $params) | ||
</pre> | </pre> | ||
+ | |||
+ | =Errors= | ||
+ | |||
+ | {| class="wikitable" width="100%" | ||
+ | ! width="5%"|Code | ||
+ | ! width="95%"|Description | ||
+ | |- | ||
+ | |<code>BXSQ0001</code> | ||
+ | |An SQL exception occurred (e.g.: a non-existing relation is retrieved). | ||
+ | |- | ||
+ | |<code>BXSQ0002</code> | ||
+ | |A wrong connection handle or prepared statement handle is passed. | ||
+ | |- | ||
+ | |<code>BXSQ0003</code> | ||
+ | |The number of <code><sql:parameter/></code> elements in <code><sql:parameters/></code> differs from the number of placeholders in the prepared statement. | ||
+ | |- | ||
+ | |<code>BXSQ0004</code> | ||
+ | |The type of a parameter for a prepared statement is not specified. | ||
+ | |- | ||
+ | |<code>BXSQ0005</code> | ||
+ | |An attribute different from <code>type</code> and <code>null</code> is set for a <code><sql:parameter/></code> element. | ||
+ | |- | ||
+ | |<code>BXSQ0006</code> | ||
+ | |A parameter is from type date, time or timestamp and its value is in an invalid format. | ||
+ | |- | ||
+ | |<code>BXSQ0007</code> | ||
+ | |A specified database driver class is not found. | ||
+ | |} | ||
=Changelog= | =Changelog= |
Revision as of 02:08, 26 May 2012
This XQuery Module contains functions to access relational databases from XQuery using SQL. With this module, you can execute query, update and prepared statements, and the result sets are returned as sequences of XML elements representing tuples. Each element has children representing the columns returned by the SQL statement.
Contents
Conventions
All functions in this module are assigned to the http://basex.org/modules/sql
namespace, which is statically bound to the sql
prefix.
All errors are assigned to the http://basex.org/errors
namespace, which is statically bound to the bxerr
prefix.
Functions
sql:init
Signatures | sql:init($class as xs:string) as empty-sequence()
|
Summary | This function initializes a JDBC driver specified via $class . This step might be superfluous if the SQL database is not embedded. |
Errors | BXSQ0007 is raised if the specified driver class is not found. |
sql:connect
Signatures | sql:connect($url as xs:string) as xs:integer sql:connect($url as xs:string, $user as xs:string, $password as xs:string) as xs:integer sql:connect($url as xs:string, $user as xs:string, $password as xs:string, $options as item()) as xs:integer |
Summary | This function establishes a connection to a relational database. As a result a connection handle is returned. The parameter $url is the URL of the database and shall be of the form: jdbc:<driver name>:<server> [/<database> . If the parameters $user and $password are specified, they are used as credentials for connecting to the database. The parameter $options can be used to set connection options, e.g. auto-commit mode. It can be specified as:
|
Errors | BXSQ0001 is raised if an SQL exception occurs, e.g. missing JDBC driver or not existing relation. |
sql:execute
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.
Signatures | sql:execute($connection as xs:integer, $item as item()) as element()*
|
Summary | This function executes a query, update or prepared statement. The parameter $id specifies either a connection handle or a prepared statement handle. The parameter $item is either a string representing an SQL statement or an element <sql:parameters/> representing the parameters for a prepared statement along with their types and values. In case of the latter, the following schema shall be used:element sql:parameters { element sql:parameter { attribute type { "int"|"string"|"boolean"|"date"|"double"|"float"|"short"|"time"|"timestamp" }, attribute null { "true"|"false" }?, text }+ }? |
Errors | BXSQ0001 is raised if an SQL exception occurs, e.g. not existing relation is retrieved. BXSQ0002 is raised if a wrong connection handle or prepared statement handle is passed. |
sql:prepare
Signatures | sql:prepare($connection as xs:integer, $statement as xs:string) as xs:integer
|
Summary | This function prepares a statement and returns a handle to it. The parameter $connection indicates the connection handle to be used. The parameter $statement is a string representing an SQL statement with one or more '?' placeholders. If the value of a field has to be set to NULL , then the attribute null of the element <sql:parameter/> has to be true .
|
Errors | BXSQ0001 is raised if an SQL exception occurs. BXSQ0002 is raised if a wrong connection handle is passed. |
sql:commit
Signatures | sql:commit($connection as xs:integer) as empty-sequence()
|
Summary | This function commits the changes made to a relational database. $connection specifies the connection handle.
|
Errors | BXSQ0001 is raised if an SQL exception occurs. BXSQ0002 is raised if a wrong connection handle is passed. |
sql:rollback
Signatures | sql:rollback($connection as xs:integer) as empty-sequence()
|
Summary | This function rolls back the changes made to a relational database. $connection specifies the connection handle.
|
Errors | BXSQ0001 is raised if an SQL exception occurs. BXSQ0002 is raised if a wrong connection handle is passed. |
sql:close
Signatures | sql:close($connection as xs:integer) as empty-sequence()
|
Summary | This function closes a connection to a relational database. $connection specifies the connection handle.
|
Errors | BXSQ0001 is raised if an SQL exception occurs. BXSQ0002 is raised if a wrong connection handle is passed. |
Examples
Direct queries
A simple select statement can be executed on the following way:
let $conn := sql:connect("jdbc:postgresql://localhost:5432/coffeehouse") return sql:execute($conn, "SELECT * FROM coffees WHERE price < 10")
The result will look like:
<sql:row xmlns:sql="http://basex.org/modules/sql"> <sql:column name="cof_name">French_Roast</sql:column> <sql:column name="sup_id">49</sql:column> <sql:column name="price">9.5</sql:column> <sql:column name="sales">15</sql:column> <sql:column name="total">30</sql:column> </sql:row> <sql:row xmlns:sql="http://basex.org/modules/sql"> <sql:column name="cof_name">French_Roast_Decaf</sql:column> <sql:column name="sup_id">49</sql:column> <sql:column name="price">7.5</sql:column> <sql:column name="sales">10</sql:column> <sql:column name="total">14</sql:column> </sql:row> <sql:row xmlns:sql="http://basex.org/modules/sql"> <sql:column name="cof_name">Colombian_Decaf</sql:column> <sql:column name="sup_id">101</sql:column> <sql:column name="price">8.75</sql:column> <sql:column name="sales">6</sql:column> <sql:column name="total">12</sql:column> <sql:column name="date">2010-10-10 13:56:11.0</sql:column> </sql:row>
Prepared Statements
A prepared select statement can be executed in the following way:
(: Establish a connection :) let $conn := sql:connect("jdbc:postgresql://localhost:5432/coffeehouse") (: Obtain a handle to a prepared statement :) let $prep := sql:prepare($conn, "SELECT * FROM coffees WHERE price < ? AND cof_name = ?") (: Values and types of prepared statement parameters :) let $params := <sql:parameters> <sql:parameter type='double'>10</sql:parameter> <sql:parameter type='string'>French_Roast</sql:parameter> </sql:parameters> (: Execute prepared statement :) return sql:execute($prep, $params)
Errors
Code | Description |
---|---|
BXSQ0001
|
An SQL exception occurred (e.g.: a non-existing relation is retrieved). |
BXSQ0002
|
A wrong connection handle or prepared statement handle is passed. |
BXSQ0003
|
The number of <sql:parameter/> elements in <sql:parameters/> differs from the number of placeholders in the prepared statement.
|
BXSQ0004
|
The type of a parameter for a prepared statement is not specified. |
BXSQ0005
|
An attribute different from type and null is set for a <sql:parameter/> element.
|
BXSQ0006
|
A parameter is from type date, time or timestamp and its value is in an invalid format. |
BXSQ0007
|
A specified database driver class is not found. |
Changelog
The module was introduced with Version 7.0.