I am using Sybase 11 with Hibernate 3.05 and receive the following error when I try to execute the following code using a named query.

try
{
Session session = HibernateUtilSimple.currentSession();

List acctStatusList = session.getNamedQuery("getAccountStatus").list();
logger.info("Size of List is : " + acctStatusList.size());
HibernateUtilSimple.closeSession();
}


<hibernate-mapping package="com.ssmb.esales.account.model" auto-import="true" default-lazy="false">
<class name="AccountStatusSummary">
<id name="accountId" column="AccountId"></id>
</class>

<!-- Here's A Sample Of How to Declare the Stored Procedure -->
<sql-query name="getAccountStatus" callable="true">
<return alias="" class="AccountStatusSummary">
<return-property name="accountId" column="ActI"/>
<return-property name="accountMnc" column="ActMnc"/>
<return-property name="cpiNum" column="CpiNum"/>
<return-property name="currentStatusCode" column="CurrentStatusCode"/>
<return-property name="gfcId" column="Gfcid"/>
<return-property name="imsNum" column="ActIMSNum"/>
<return-property name="legalEntityName" column="ActDesc"/>
</return>

{ ? = call getGfcidRequestTb("CurrentStatusCode","Not Acknowledged") }
</sql-query>
</hibernate-mapping>


2005-09-19 12:40:54,825 ERROR [org.hibernate.util.JDBCExceptionReporter] - <Stored procedure 'getGfcidRequestTb' may be run only in unchained transaction mode. The 'SET CHAINED OFF' command will cause the current session to use unchained transaction mode.

What do I need to do to fix this ?

Thanks
David

i used google and found an answer in seconds....why dont you try the same ?

hint: the error is sybase specific and has to do with the default mode sybase runs stored procedures and transactions in.

Max -
If you are alluding to the fact that the Sybase Database Configuration opens a transaction by default then I am aware of that. (SET CHAINED OFF) Given that I cannot change the database configuration of our database ( that is fixed in the production environment). That is why I asked the question. Thinking that there may be a property that I can set in Hibernate to tell it not to do this when it open the Session.

Just as a side note. Instead of chatising me for not "using google" would not it have been more productive to simply give me a straight answer rather than chidding me like some bad child for not doing exactly what you did.

David

well, since you just pasted mappings with an exceptions asking "What do I need to do to fix this" then it looked to me like you didn't even chekked for SET CHAINED OFF ...if you had taken you the 3 seconds extra to write the question about wether there exist and option for you to control the connection settings then I could have answered immediatly with:

Use session.connection() to execute whatever JDBC required to change this state and if that is not enough then write your own implementation of ConnectionProvider that does the setup you need.

(and sorry if you felt offended but we get about 100 postings a day and 90% are questions easily answerable via google or rereading the docs)

Max -
Now that was a useful post.

Thanks
David

(yes - but still much quicker answered via reread docs and google IMO ;)