Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 52376 invoked from network); 16 Feb 2008 10:58:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Feb 2008 10:58:15 -0000 Received: (qmail 48548 invoked by uid 500); 16 Feb 2008 10:58:08 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 48517 invoked by uid 500); 16 Feb 2008 10:58:08 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 48506 invoked by uid 99); 16 Feb 2008 10:58:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Feb 2008 02:58:08 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ussraf@gmail.com designates 209.85.146.181 as permitted sender) Received: from [209.85.146.181] (HELO wa-out-1112.google.com) (209.85.146.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Feb 2008 10:57:36 +0000 Received: by wa-out-1112.google.com with SMTP id m38so1948047waf.5 for ; Sat, 16 Feb 2008 02:57:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=psyGI+RhWADhs/ANurkbEfOc2UA0Y9AdXJdamstdd0E=; b=Aja8nK3IqRhud2dQzLQonU/tzr0YCazEsNqnyx2+vw5btfGVD8U/h8rpTbLXhueNdPnSt+D2fCKAA3blY9N2jX79p3zHt7IZpfazhJ8BIYfywPsN2TsmHH7THs/lkCBuxONFjErjJ8myyPoCMdcNSYqU7vaRK7BOtUCQrLuWC0o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=b/gFF1MIdQFg8HUEcSlecSOz5BlcrSexMoUi3pcBSlNhmHxYreYpIWLwI1bJcl0PR2AUm0UKErGdkn4x8i8qIQ0D/Zgfkt7MPjNj1TEDlMnhTemFI+j/9CWVTVFnAhCErn+OQ1QJRnE/PL0fPBRJ2MBPkxiotz1NWze8IL/b+qc= Received: by 10.114.130.1 with SMTP id c1mr4127593wad.52.1203159464979; Sat, 16 Feb 2008 02:57:44 -0800 (PST) Received: by 10.114.181.5 with HTTP; Sat, 16 Feb 2008 02:57:44 -0800 (PST) Message-ID: <18db29d30802160257h1d365a91y864eaf28cab7e323@mail.gmail.com> Date: Sat, 16 Feb 2008 18:57:44 +0800 From: "sin(EaTing)," To: "Derby Discussion" Subject: Re: Transaction Problems of a Derby Stored Procedure In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1776_26297274.1203159464967" References: <18db29d30802141915v5b9bfafaufadd73d5e4a9f888@mail.gmail.com> <47B5B6E6.6080905@apache.org> <18db29d30802151900g5f02e9vc5c88d432c77969a@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_1776_26297274.1203159464967 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline That's great. Thanks. On Feb 16, 2008 6:51 PM, wrote: > "sin(EaTing)," writes: > > > Thanks, Dan. > > The document I read seems already the latest, which is Derby Developer's > > Guide Version 10.3. > > And I am still confused about the isolation mode, I traced the stored > > procedure using getTransactionIsolation() and the return value shows the > > isolation level was changed, I am not sure about the whether that data > can > > reflect the real isolation level. > > I think that the documentation is incorrect here. It is possible to > modify the isolation level in both a function and a procedure, but not > while a cursor is open because changing the isolation level will commit > the current transaction. > > You can see a Derby JUnit test which modifies the > isolation level in a number of ways here > > > http://svn.apache.org/repos/asf/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/CacheSessionDataTest.java > > > -- > dt > ------=_Part_1776_26297274.1203159464967 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline That's great. Thanks.

On Feb 16, 2008 6:51 PM, <Dyre.Tjeldvoll@sun.com> wrote:
"sin(EaTing)," <ussraf@gmail.com> writes:

> Thanks, Dan.
> The document I read seems already the latest, which is Derby Developer's
> Guide Version 10.3.
> And I am still confused about the isolation mode, I traced the stored
> procedure using getTransactionIsolation() and the return value shows the
> isolation level was changed, I am not sure about the whether that data can
> reflect the real isolation level.

I think that the documentation is incorrect here. It is possible to
modify the isolation level in both a function and a procedure, but not
while a cursor is open because changing the isolation level will commit
the current transaction.

You can see a Derby JUnit test which modifies the
isolation level in a number of ways here

http://svn.apache.org/repos/asf/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/CacheSessionDataTest.java


--
dt

------=_Part_1776_26297274.1203159464967--