Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (nike.apache.org: domain of rickcr@gmail.com designates
 74.125.78.145 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=bIHGAQLWpGdg13h11zWDw4yhPD+QCn61chMCQaLwVD5KiRQCCSRl7mh2r8WjBY25+h
         VGfdIketLY/1YDlb/jKe+5MwrA0I55QiNFkoxaJCDfoyfwEjNqsierDZ4777Iy3lvemu
         nB0Sz3a4xzIcJeiOJUYm58Axoer1qk6qj65xU=
MIME-Version: 1.0
In-Reply-To: <16178eb10908231332n524724e6wb34a883a6b6037f2@mail.gmail.com>
References: <583d4dff0908231323k75e59ab8se4db6177d4597cde@mail.gmail.com>
	 <16178eb10908231332n524724e6wb34a883a6b6037f2@mail.gmail.com>
Date: Sun, 23 Aug 2009 16:46:55 -0400
Message-ID: <583d4dff0908231346y63866b73ga85df41dc7cc883d@mail.gmail.com>
Subject: Re: confusing on caching prepared statements with datasource and
	openSession?
From: Rick <rickcr@gmail.com>
To: user-java@ibatis.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

So just for my own understanding... If I configured a datasource that
uses pstmt caching (which for example c3p0 can do on a per-connection
basis, which isn't a standard implementation I know), can I just not
even bother opening a Session in iBATIS with ExecutorType.REUSE and
I'd still get caching implemented by the underlying datasource? Sounds
like I'm best not even worrying about it and just use openSession().


On Sun, Aug 23, 2009 at 4:32 PM, Clinton Begin<clinton.begin@gmail.com> wro=
te:
> iBATIS only caches at the connection level anyway.=A0 The broad support f=
or
> this is lacking, so I just avoided the problem.
>
> 99% of the gain with psmt caching is in loops in a single thread anyway..=
..
>
> Clinton
>
> On Sun, Aug 23, 2009 at 2:23 PM, Rick <rickcr@gmail.com> wrote:
>>
>> I thought that most datasources allow you to cache preparedStatements
>> at the datasource level, so I'm confused what affect using
>> sqlSessionFactory.openSession(ExecutorType.REUSE) would be if you
>> have, or don't have, your datasource set to cache pstmts and you call
>> (and not call) openSession with ExecutorType.REUSE ?
>>
>> --
>> Rick R
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
>> For additional commands, e-mail: user-java-help@ibatis.apache.org
>>
>
>


--=20
Rick R

---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org