[jira] Reopened: (DERBY-1158) Allow use of Statements created in local transaction with default holdability to be used in global transactions.

2006-04-24 Thread Andrew McIntyre (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1158?page=all ] Andrew McIntyre reopened DERBY-1158: Allow use of Statements created in local transaction with default holdability to be used in global transactions

[jira] Closed: (DERBY-1158) Allow use of Statements created in local transaction with default holdability to be used in global transactions.

2006-04-24 Thread Andrew McIntyre (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1158?page=all ] Andrew McIntyre closed DERBY-1158: -- Fix Version: 10.1.3.0 Resolution: Fixed Allow use of Statements created in local transaction with default holdability to be used in global

[jira] Reopened: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

2006-04-11 Thread Mamta A. Satoor (JIRA)
default holdability of HOLD_CURSORS_OVER_COMMIT is not restored. -- Key: DERBY-366 URL: http://issues.apache.org/jira/browse

[jira] Closed: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

2006-04-11 Thread Mamta A. Satoor (JIRA)
transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored. -- Key: DERBY-366 URL: http://issues.apache.org

[jira] Resolved: (DERBY-1158) Allow use of Statements created in local transaction with default holdability to be used in global transactions.

2006-04-07 Thread Daniel John Debrunner (JIRA)
use of Statements created in local transaction with default holdability to be used in global transactions. Key: DERBY-1158 URL: http://issues.apache.org/jira

[jira] Created: (DERBY-1158) Allow use of Statements created in local transaction with default holdability to be used in global transactions.

2006-03-28 Thread Daniel John Debrunner (JIRA)
Allow use of Statements created in local transaction with default holdability to be used in global transactions. Key: DERBY-1158 URL: http://issues.apache.org/jira

[jira] Assigned: (DERBY-1158) Allow use of Statements created in local transaction with default holdability to be used in global transactions.

2006-03-28 Thread Daniel John Debrunner (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-1158?page=all ] Daniel John Debrunner reassigned DERBY-1158: Assign To: Daniel John Debrunner Allow use of Statements created in local transaction with default holdability to be used in global

[jira] Commented: (DERBY-1158) Allow use of Statements created in local transaction with default holdability to be used in global transactions.

2006-03-28 Thread Daniel John Debrunner (JIRA)
transaction with default holdability to be used in global transactions. Key: DERBY-1158 URL: http://issues.apache.org/jira/browse/DERBY-1158 Project: Derby

Re: default holdability

2006-02-24 Thread Mike Matrigali
I agree with Bernt that I find it surprising that users depend on resultsets being holdable, but my experience is that there are many applications out there where this is the case. I am not going to try to argue what is right (personally I cringe at what kind of consistency those clients are

default holdability

2006-02-22 Thread Andreas Korneliussen
HOLD_CURSORS_OVER_COMMIT. I think Derby is architected to support the holdability mode CLOSE_CURSOR_AT_COMMIT by all combinations of ResultSets. I therefore find it reasonable to consider changing the *default* holdability mode from HOLD_CURSORS_OVER_COMMIT to CLOSE_CURSORS_AT_COMMIT

Re: default holdability

2006-02-22 Thread Dag H. Wanvik
Hi, Daniel John Debrunner [EMAIL PROTECTED] writes: The JDBC 3.0 spec is silent on this, sections 14.1.1 and 14.1.2 describe what can be done when a ResultSet type or concurrency is not supported. However in 14.1.3 there is no comment about what can be done when a requested holdability is

Re: default holdability

2006-02-22 Thread Lance J. Andersen
t support holdable result sets then I think that's a great first step. I think Derby is architected to support the holdability mode CLOSE_CURSOR_AT_COMMIT by all combinations of ResultSets. I therefore find it reasonable to consider changing the *default* holdability mode

Re: default holdability

2006-02-22 Thread Bernt M. Johnsen
Hi all, Allthough I agree that backwards compatability is important, I find the current default unfortunate for several reasons: 1) As Anreas points out: The architecture seems to be designed for non-holdable cursors (in agreement with the old Cloudscape default). 2) Cursors in the SQL

Re: default holdability

2006-02-22 Thread Satheesh Bandaram
I don't think changing default holdability is a good idea... like Dan and Dag mentioned. Why does Derby have to change default holdability because SUR and XA can't support it? Also Derby doesn't have SQL cursors, only JDBC cursors, right? Even if default is changed, SUR and XA will still

Re: default holdability

2006-02-22 Thread Kathey Marsden
but the way I think it has to stay. *-1* to changing the default holdability We have to have a seamless upgrade that does not require application changes. It is essential to the sustainability of Derby. I have said this many times before but perhaps have not explained why, so I'll go into some

Re: default holdability

2006-02-22 Thread Daniel John Debrunner
Kathey Marsden wrote: I think ultimately if we can support loading Derby in multiple class loaders, we document how to do that, and we get our installed user base doing it that way be default, we will have more flexibility. For now we don't have it. Still I would vote -1 on this one. The

[jira] Resolved: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

2005-06-22 Thread Mamta A. Satoor (JIRA)
Project: Derby Type: Bug Components: JDBC Versions: 10.0.2.1 Reporter: Mamta A. Satoor Assignee: Mamta A. Satoor Attachments: Derby8_Derby366_061805.txt, mamta.java A connection in local transaction has a default holdability of HOLD_CURSORS_OVER_COMMIT. When

[jira] Closed: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

2005-06-22 Thread Mamta A. Satoor (JIRA)
[ http://issues.apache.org/jira/browse/DERBY-366?page=all ] Mamta A. Satoor closed DERBY-366: - In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT

[jira] Commented: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

2005-06-21 Thread Kathey Marsden (JIRA)
global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored. -- Key: DERBY-366

[jira] Updated: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

2005-06-18 Thread Mamta A. Satoor (JIRA)
object from XAConnection inside the global transaction) and Derby-366 (In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.) The patch is attached to both Derby-8 and Derby-366. The fix for both

[jira] Updated: (DERBY-366) In jdk13, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored.

2005-06-15 Thread Mamta A. Satoor (JIRA)
, when a connection transitions from global transaction to local transaction, its default holdability of HOLD_CURSORS_OVER_COMMIT is not restored