Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

*** empty log message *** 

git-svn-id: https://svn.jboss.org/repos/hibernate/trunk/Hibernate3/doc@6152 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Max Rydahl Andersen 2005-03-22 07:36:07 +00:00
parent f78f6ab859
commit e1e8adccd4
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
reference/en/modules/query_sql.xml
View File

@ -234,6 +234,31 @@ BEGIN
Notice stored procedures currently only return scalars and entities. <literal>&gt;return-join&lt;</literal> and
<literal>&gt;load-collection&lt;</literal> is not supported.
</para>
<para>
TODO: make the "rules" visually nicer and understandable ,)
</para>
<sect3>
<title>Rules/Limitations for using stored procedures</title>
<para>
To use stored procedures with Hibernate the procedures have to follow some rules. If they do not follow those
rules they are not usable with Hibernate. If you still want to use these procedures you have to execute them via <literal>session.connection()</literal>.
The rules are different per database since database vendors have different stored procedure semantics/syntax.
For Oracle the following rules applies:
1. It must return a result set. (This is done by returning a SYS_REFCURSOR in Oracle 9 & 10, in Oracle you need to define a REF CURSOR type)
2. It should be on the form <literal>{ ? = call procName(<parameters>) }</literal> or <literal>{ ? = call procName}</literal> (this is more a Oracle rule than a Hibernate rule)
For Sybase & MS SQL server the following rules applies:
It must return a result set. Note that since these servers can/will return multiple result sets and update count Hibernate will iterate the results and take the first result that is a result set as its return value. Everything else will be discarded.
If you can enable SET NOCOUNT ON in your procedure it will probably be the most efficient, but it is not an requirement.
</para>
</sect3>
</sect2>
</sect1>