ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mkhitaryan, Aram" <Aram.Mkhitar...@lycos-europe.com>
Subject RE: jdbcType cursor
Date Wed, 23 Aug 2006 04:19:23 GMT
I’m not sure, but you can try to add your driver properties in database URL in IBATIS configurations.

It works with MySQL driver, I think it will work also with MSSQL driver.

 

Best,

Aram

 

________________________________

From: Celaya, Tina (GE Indust, ConsInd) [mailto:tina.celaya@ge.com] 
Sent: Tuesday, August 22, 2006 7:10 PM
To: user-java@ibatis.apache.org
Cc: clinton.begin@gmail.com
Subject: RE: jdbcType cursor

 

Hello Clinton, i downloaded the ibatis 2.2.0 on the ibatis web page, and replaced the ibatis
jars i had for the 2.2.0 and i´m trying to run mi web application and i cant past the login
page, and it was fine before i upgraded, im having this error java.sql.SQLException: [Microsoft][SQLServer
2000 Driver for JDBC]Can't start a cloned connection while in manual transaction mode. and
i search it and i found the following information on microsoft support web page:  

 


CAUSE


This error occurs when you try to execute multiple statements against a SQL Server database
with the JDBC driver while in manual transaction mode (AutoCommit=false) and while using the
direct (SelectMethod=direct) mode. Direct mode is the default mode for the driver. 


RESOLUTION


When you use manual transaction mode, you must set the SelectMethod property of the driver
to Cursor, or make sure that you use only one active statement on each connection as specified
in the "More Information" section of this article.  

 

but i dont really know where to set this properties and why my application works with the
old jars and not with the new ones.....

 

can you help me?

	-----Original Message-----
	From: Clinton Begin [mailto:clinton.begin@gmail.com]
	Sent: Domingo, 20 de Agosto de 2006 10:37 p.m.
	To: user-java@ibatis.apache.org
	Subject: Re: jdbcType cursor

	
	Upgrade to 2.2.0 and ust "cursor" or "java.sql.ResultSet".  
	
	Clinton

	On 8/18/06, Celaya, Tina (GE Indust, ConsInd) < tina.celaya@ge.com <mailto:tina.celaya@ge.com>
> wrote: 

	Hello, does any one know what to put in de jdbcType in this statement 
	<parameter property="results" jdbcType="ORACLECURSOR" mode="OUT"/>
	insted of ORACLECURSOR if i´m using microsoft sql DB?
	thanks for your help
	
	-----Original Message----- 
	From: larry.meadors@gmail.com [mailto: larry.meadors@gmail.com <mailto:larry.meadors@gmail.com>
]On Behalf
	Of Larry Meadors
	Sent: Viernes, 18 de Agosto de 2006 09:52 a.m.
	To: user-java@ibatis.apache.org
	Subject: Re: Nested Bean in Result Map
	
	
	This works: 
	
	<resultMap id="PageBeanRM" class="PageBean"> 
	<result property="id"  column="ID" />
	<result property="name"  column="NAME" />
	<result property="detail.address1" column="ADDRESS1" /> 
	<result property="detail.address2" column="ADDRESS2" />
	</resultMap>
	
	Larry
	
	
	On 8/18/06, kiran.gutta@wipro.com < kiran.gutta@wipro.com <mailto:kiran.gutta@wipro.com>
> wrote:
	>
	>
	>
	> Hi,
	>
	> I have a bean as shown below.
	>
	> class PageBean{
	>     int id;
	>     NestedBean detail;
	>     String name; 
	> }
	>
	> class NestedBean{
	>     String address1;
	>     String address2;
	> }
	>
	> I have table with following columns.
	> ID, NAME, ADDRESS1, ADDRESS2
	>
	> How to set the result map for the PageBean? 
	>
	> Thanks & Regards,
	> Kiran
	>
	>
	>
	>  The information contained in this electronic message and any attachments to this message
are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential
or privileged information. If you are not the intended recipient, you should not disseminate,
distribute or copy this e-mail. Please notify the sender immediately and destroy all copies
of this message and any attachments. 
	>
	>  WARNING: Computer viruses can be transmitted via email. The recipient should check
this email and any attachments for the presence of viruses. The company accepts no liability
for any damage caused by any virus transmitted by this email. 
	>
	>  www.wipro.com
	>

	 

Mime
View raw message