You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by ha...@apache.org on 2002/08/09 10:22:45 UTC
cvs commit: xml-cocoon2/src/documentation/xdocs/userdocs/xsp esql.xml
haul 2002/08/09 01:22:45
Modified: src/documentation/xdocs/userdocs/xsp esql.xml
Log:
Update docs: connection properties, stored procedures
Revision Changes Path
1.8 +32 -3 xml-cocoon2/src/documentation/xdocs/userdocs/xsp/esql.xml
Index: esql.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/userdocs/xsp/esql.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- esql.xml 28 Jun 2002 08:02:56 -0000 1.7
+++ esql.xml 9 Aug 2002 08:22:45 -0000 1.8
@@ -55,6 +55,33 @@
. . .
</xsp:page>
]]></source>
+
+ <s2 title="Connection">
+ <p>Esql can use connection pools configured in <code>cocoon.xconf</code> or
+ individually set up connections.</p>
+
+ <p><code>esql:pool</code> gives the name of the connection pool to use.</p>
+
+ <p>Individually configured connections use the <code>esql:driver,
+ esql:dburl, esql:username, esql:password</code> tags. Their meaning
+ should be obvious.</p>
+
+ <s3 title="Connection Options"/>
+ <p>Per default, esql will try to switch a connection to <em>autocommit</em>
+ mode. This is because it prevents hanging transactions that hold locks and
+ disturb further database accesses. Esql can be forced to not use
+ autocommit, by giving the
+ <code><esql:autocommit>false</esql:autocommit></code> nested
+ element to <code>esql:connection</code>.</p>
+
+ <note>Even if a connection is configured with autocommit off in
+ <code>cocoon.xconf</code>, esql will switch autocommit on if not
+ instructed to do otherwise.</note>
+
+ <p>Other options like limiting the size of the resultset are discussed
+ below.</p>
+ </s2>
+
</s1>
<s1 title="Usage and Examples">
@@ -295,9 +322,11 @@
For a more general alternative see further below.</p>
<p>Parameters for a stored procedure call may be of
- <code>direction="in|out|inout"</code> with the usual JDBC meaning. In
- addition a <code>type</code> needs to be supplied as well. This would be
- the same "XXX" as used in a <code>get-XXX</code> JDBC-method call.</p>
+ <code>direction="in|out|inout"</code> with the usual JDBC meaning. In
+ addition a <code>type</code> needs to be supplied for "out" and "inout"
+ parameters. This would be the same "XXX" as used in a <code>get-XXX</code>
+ JDBC-method call. Alternatively, you can use a fully qualified field name,
+ e.g. "java.sql.Types.CHAR"</p>
<p><code><esql:call-results/></code> (child of
<code><esql:execute-query/></code>) may contain code that will
----------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org