[
https://issues.apache.org/jira/browse/DERBY-827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485998
]
Dyre Tjeldvoll commented on DERBY-827:
--
Status report: I currently see 6 failures when
running derbyall:
Implement the XA transaction support for embedded driver.
-
Key: DERBY-2508
URL: https://issues.apache.org/jira/browse/DERBY-2508
Project: Derby
Issue Type: Sub-task
Affects
Implement the XA transaction support for client driver.
---
Key: DERBY-2509
URL: https://issues.apache.org/jira/browse/DERBY-2509
Project: Derby
Issue Type: Sub-task
Affects Versions:
[
https://issues.apache.org/jira/browse/DERBY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486029
]
Rick Hillegas commented on DERBY-2109:
--
Hi Dan,
Sorry for not responding to your January 26 comment sooner. I
[
https://issues.apache.org/jira/browse/DERBY-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486030
]
quartz commented on DERBY-2451:
---
As it stands, the affected versions are not acceptable because if a db client
can
Issue Subscription
Filter: Derby: JIRA issues with patch available (21 issues)
Subscriber: derby-dev
Key Summary
DERBY-2114 Let Clock embed a HashMap rather than inherit from Hashtable
https://issues.apache.org/jira/browse/DERBY-2114
DERBY-2416 Provide collation sensitive
[Auto-generated mail]
*Daily* 524622/2007-04-01 18:00:27 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0370370 080.35% derbyall
072807280 0 595.45% suitesAll
sles
0
[
https://issues.apache.org/jira/browse/DERBY-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486075
]
Kathey Marsden commented on DERBY-2461:
---
In converting this test I found what I think may be a bug, but I am
Network server does not release locks on commit and getMoreResults if multiple
resultsets are returned by a stored procedure
-
Key: DERBY-2510
reference manual's description of JDBC4 features has misleading sections
Key: DERBY-2511
URL: https://issues.apache.org/jira/browse/DERBY-2511
Project: Derby
Issue
[
https://issues.apache.org/jira/browse/DERBY-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486141
]
Øystein Grøvlen commented on DERBY-2495:
Junit suit and derbyall was run with no errors, except the one that
[
https://issues.apache.org/jira/browse/DERBY-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre resolved DERBY-2476.
Resolution: Fixed
Committed to trunk with revision 524933.
convert lang/forbitdata.java
Network client should not allow prepare of a stored procedure with an output
parameter using a PreparedStatement
Key: DERBY-2512
URL:
[
https://issues.apache.org/jira/browse/DERBY-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486146
]
Øystein Grøvlen commented on DERBY-2510:
What kind of locks are we talking about here? I would assume that
[
https://issues.apache.org/jira/browse/DERBY-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A B resolved DERBY-1852.
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: [Existing Application Impact] (was: [Existing
Network client allows OUT param to be set to a value
Key: DERBY-2513
URL: https://issues.apache.org/jira/browse/DERBY-2513
Project: Derby
Issue Type: Bug
Components: Network
In the current work to use locators for LOBs on client, we have defined
a set of stored procedures that will be called to operate on the LOBs at
the server (ref. DERBY-208).
Testing my experimental code for locator support, shows that my
implementation has problems with auto-commit mode. One
Network client does not retain the INOUT parameter value change for subsequent
execution
Key: DERBY-2515
URL: https://issues.apache.org/jira/browse/DERBY-2515
[
https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486173
]
Daniel John Debrunner commented on DERBY-2514:
--
Some of the existing JUNit tests added for JDBC 4 do
[
https://issues.apache.org/jira/browse/DERBY-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre updated DERBY-2467:
---
Derby Info: (was: [Patch Available])
Hi Ugo,
I took a closer look at the test, a few
Network Client allows execution of callable statement when one of the
parameters is not set
---
Key: DERBY-2516
URL: https://issues.apache.org/jira/browse/DERBY-2516
[
https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486181
]
Ramandeep Kaur commented on DERBY-2514:
---
Dan, when you said if coverage already exists, did you mean by code
convert lang/forupdate.sql to junit
Key: DERBY-2517
URL: https://issues.apache.org/jira/browse/DERBY-2517
Project: Derby
Issue Type: Test
Components: Test
Reporter: Ramandeep Kaur
convert lang/releaseCompileLocks.sql to junit
--
Key: DERBY-2518
URL: https://issues.apache.org/jira/browse/DERBY-2518
Project: Derby
Issue Type: Test
Components: Test
[Auto-generated mail]
*tinderbox_trunk16* 524934/2007-04-02 23:42:56 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0369369 097.59% derbyall
F:1,E:072907289 0
Hi,
I have created subclasses for SQLChar and rest of the character data types.
These subclasses will use the Collator passed to them in the constructor for
collation.
For the next incremental step, I am looking at adding collation type and
collation derivation in the DataTypeDescriptor(DTD).
[Auto-generated mail]
*tinderbox_trunk16* 524991/2007-04-03 03:22:41 CEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
SunOS-5.10_i86pc-i386
0369369 097.47% derbyall
F:1,E:072907289 0
27 matches
Mail list logo