[
http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434908 ]
Knut Anders Hatlen commented on DERBY-1326:
---
Committed derby-1326-cleanup_exceptions.diff with revision 446538.
Network server may abandon sessions
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12434965 ]
Knut Anders Hatlen commented on DERBY-801:
--
I will hold the commit until Anders has responded to the questions from Suresh.
1, 2 and 3 seem like trivial
[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]
Knut Anders Hatlen updated DERBY-1326:
--
Attachment: derby-1326-skipThreads.diff
Attaching patch (derby-1326-skipThreads.diff) which modifies
NetworkServerControlImpl the same way as
[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]
Knut Anders Hatlen updated DERBY-1326:
--
Derby Info: [Patch Available]
Network server may abandon sessions when Derby system is shutdown and this
causes intermittent hangs in the client
[
http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434985 ]
Knut Anders Hatlen commented on DERBY-1326:
---
Deepa wrote:
I still cannot wrap my head around old sessions hanging around in the server.
They hang
[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]
Knut Anders Hatlen updated DERBY-1326:
--
Derby Info: (was: [Patch Available])
Thanks for the suggestions, Deepa. I committed skipThreads with revision
447375. Will post a new patch with
[
http://issues.apache.org/jira/browse/DERBY-1314?page=comments#action_12435498 ]
Knut Anders Hatlen commented on DERBY-1314:
---
PROBLEM
The behaviour of executeQuery() and executeUpdate() did not match the
JDBC specification when
[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]
Knut Anders Hatlen updated DERBY-1326:
--
Attachment: derby-1326-checkds.diff
derby-1326-checkds.diff re-enables the shutdown in checkDataSource. Without the
skipThreads patch,
[ http://issues.apache.org/jira/browse/DERBY-1832?page=all ]
Knut Anders Hatlen closed DERBY-1832.
-
sysinfo test fails with access denied (java.util.PropertyPermission
java.class.path read) when derbyclient.jar is first in classpath
[ http://issues.apache.org/jira/browse/DERBY-1817?page=all ]
Knut Anders Hatlen closed DERBY-1817.
-
Resolution: Fixed
Race condition in network server's thread pool
--
Key: DERBY-1817
[ http://issues.apache.org/jira/browse/DERBY-803?page=all ]
Knut Anders Hatlen resolved DERBY-803.
--
Resolution: Fixed
Merged to 10.2 in Rick's mega-merge.
derbynet/DerbyNetAutoStart.java test fails intermittently with
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12435752 ]
Knut Anders Hatlen commented on DERBY-801:
--
Committed v4 into trunk with revision 447815. Fixed Suresh's comments 1-3 in
RAFContainer4 before committing.
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12435798 ]
Knut Anders Hatlen commented on DERBY-801:
--
Backed out the changes for DERBY-733 with the following commands:
svn merge -r 357275:357274 .
svn merge -r
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436122 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Although embedded throws XCL12 in some cases, I don't think the client driver
needs to do the same. From
lang/timestampArith.java fails if it starts right before midnight
-
Key: DERBY-1869
URL: http://issues.apache.org/jira/browse/DERBY-1869
Project: Derby
Issue Type: Bug
[ http://issues.apache.org/jira/browse/DERBY-1869?page=all ]
Knut Anders Hatlen updated DERBY-1869:
--
Attachment: 1869.diff
The test already has code to prevent it from being run too close to midnight.
The code checks whether the time is 23:58, and
[ http://issues.apache.org/jira/browse/DERBY-1869?page=all ]
Knut Anders Hatlen closed DERBY-1869.
-
Fix Version/s: 10.3.0.0
Resolution: Fixed
Committed revision 448133.
lang/timestampArith.java fails if it starts right before midnight
[ http://issues.apache.org/jira/browse/DERBY-1757?page=all ]
Knut Anders Hatlen resolved DERBY-1757.
---
Fix Version/s: 10.2.1.0
(was: 10.2.2.0)
Resolution: Fixed
Marking the issue as resolved since the hang has not been
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436543 ]
Knut Anders Hatlen commented on DERBY-1610:
---
I'm not sure the test should be changed. The test intentionally calls setNull()
with another type and
[
http://issues.apache.org/jira/browse/DERBY-1751?page=comments#action_12436616 ]
Knut Anders Hatlen commented on DERBY-1751:
---
Hi Fernanda,
Derbyall passed on JVM 1.5, but the jdbc40 suite (DerbyNetClient, JVM 1.6 b99)
failed:
[
http://issues.apache.org/jira/browse/DERBY-1834?page=comments#action_12436750 ]
Knut Anders Hatlen commented on DERBY-1834:
---
grantRevokeDDL2.out also has a jdk16 master. Updated and committed to trunk
with revision 448833.
Correct
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12436793 ]
Knut Anders Hatlen commented on DERBY-1610:
---
I'm sorry, I didn't notice the FOR BIT DATA part. I agree with your first
comment, that csPrepStmt should
[
http://issues.apache.org/jira/browse/DERBY-1876?page=comments#action_12436809 ]
Knut Anders Hatlen commented on DERBY-1876:
---
Moving one level down in the code and looking at the internal ResultSet
hierarchy (not java.sql.ResultSet)
[
http://issues.apache.org/jira/browse/DERBY-1826?page=comments#action_12436836 ]
Knut Anders Hatlen commented on DERBY-1826:
---
Committed revision 448900. I'm leaving the issue open until it has been
committed to the 10.2 branch.
Add
[
http://issues.apache.org/jira/browse/DERBY-1876?page=comments#action_12437015 ]
Knut Anders Hatlen commented on DERBY-1876:
---
To get an impression of the allocation/gc cost for the statistics, I made all
the runtime statistics fields
I18N tests fail on Linux/JVM 1.4.2 when derbyclient.jar is the first element of
the classpath
-
Key: DERBY-1883
URL: http://issues.apache.org/jira/browse/DERBY-1883
[ http://issues.apache.org/jira/browse/DERBY-1883?page=all ]
Knut Anders Hatlen updated DERBY-1883:
--
Attachment: 1883.diff
Seems like a security manager issue. At least, the attached patch (1883.diff),
which grants derbyclient.jar permission to
[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]
Knut Anders Hatlen updated DERBY-1326:
--
Attachment: derby-1326-restartTest.diff
Attaching a patch which makes derbynet/ShutDownDBWhenNSShutsDownTest.junit run
the repro (Restart.java) as
[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]
Knut Anders Hatlen resolved DERBY-1326.
---
Fix Version/s: 10.2.1.5
10.3.0.0
Resolution: Fixed
Committed derby-1326-restartTest.diff with revision 449616. Marking
[ http://issues.apache.org/jira/browse/DERBY-1751?page=all ]
Knut Anders Hatlen resolved DERBY-1751.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks to Fernanda for fixing the problem and to
[ http://issues.apache.org/jira/browse/DERBY-1883?page=all ]
Knut Anders Hatlen closed DERBY-1883.
-
Fix Version/s: 10.3.0.0
Resolution: Fixed
Assignee: Knut Anders Hatlen
Committed revision 449930.
I18N tests fail on Linux/JVM
[ http://issues.apache.org/jira/browse/DERBY-1430?page=all ]
Knut Anders Hatlen resolved DERBY-1430.
---
Fix Version/s: (was: 10.2.2.0)
Resolution: Invalid
Marking as invalid since the logs indicate that multiple network tests were
[
http://issues.apache.org/jira/browse/DERBY-790?page=comments#action_12438128 ]
Knut Anders Hatlen commented on DERBY-790:
--
Hi Francois,
I think the patch might be a little too simple. When sqlca_ is made
transient (and thereby null
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12438657 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Hi Tomohito,
I tried to test all type combinations on setNull(). Seems like most of the
combinations are
[ http://issues.apache.org/jira/browse/DERBY-1889?page=all ]
Knut Anders Hatlen resolved DERBY-1889.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
The name of the test was misspelt in
storetests/st_reclaim_longcol.java fails intermittently
---
Key: DERBY-1913
URL: http://issues.apache.org/jira/browse/DERBY-1913
Project: Derby
Issue Type: Bug
Components:
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12439477 ]
Knut Anders Hatlen commented on DERBY-1610:
---
I have run tests of setNull() and setObject() on most type combinations, and I
didn't find any
[ http://issues.apache.org/jira/browse/DERBY-1910?page=all ]
Knut Anders Hatlen resolved DERBY-1910.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks, Fernanda. Committed revision 452832.
[
http://issues.apache.org/jira/browse/DERBY-1889?page=comments#action_12439863 ]
Knut Anders Hatlen commented on DERBY-1889:
---
A patch is not needed just to delete a file. I'll do that manually. I noticed
that java/testing/README.htm
[
http://issues.apache.org/jira/browse/DERBY-1889?page=comments#action_12439944 ]
Knut Anders Hatlen commented on DERBY-1889:
---
Removed lobStreams.out and committed revision 452983.
Convert jdbcapi/lobStreams.java to Junit
[ http://issues.apache.org/jira/browse/DERBY-1494?page=all ]
Knut Anders Hatlen resolved DERBY-1494.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
After the check-in of DERBY-1610, both embedded and client check type
compatibility.
[ http://issues.apache.org/jira/browse/DERBY-1501?page=all ]
Knut Anders Hatlen resolved DERBY-1501.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
With the check-in of DERBY-1610, embedded and client behave consistently.
[ http://issues.apache.org/jira/browse/DERBY-1910?page=all ]
Knut Anders Hatlen updated DERBY-1910:
--
Fix Version/s: 10.2.2.0
Merged the fix into the 10.2 branch (revision 454325).
OutOfMemoryError happens when jdbcapi/_Suite.junit was executed as
[
http://issues.apache.org/jira/browse/DERBY-1845?page=comments#action_12440846 ]
Knut Anders Hatlen commented on DERBY-1845:
---
Is this still a problem after DERBY-1910?
OutOfMemoryError when running All suite directly using JUnit
[ http://issues.apache.org/jira/browse/DERBY-790?page=all ]
Knut Anders Hatlen updated DERBY-790:
-
Attachment: Serialize.java
Thanks, the test changes look great.
The attached repro (Serialize.java) shows the problem with getMessage(). Note
that I
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12441109 ]
Knut Anders Hatlen commented on DERBY-1610:
---
There are some failures in the jdbc40 suite caused by these changes. I'll post
a patch for it.
Resolve
[ http://issues.apache.org/jira/browse/DERBY-1610?page=all ]
Knut Anders Hatlen updated DERBY-1610:
--
Attachment: derby-1610-jdk16.diff
Attaching a patch which fixes the failures in the jdbc40 suite (see
[
http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12441374 ]
Knut Anders Hatlen commented on DERBY-1610:
---
Thanks Tomohito. If the methods are static, each setter method must
call getColumnMetaDataX(),
Remove stale code from the statement classes in the client driver
-
Key: DERBY-1956
URL: http://issues.apache.org/jira/browse/DERBY-1956
Project: Derby
Issue Type: Improvement
[ http://issues.apache.org/jira/browse/DERBY-1956?page=all ]
Knut Anders Hatlen updated DERBY-1956:
--
Attachment: 1956.diff
1956.stat
Attaching a patch which removes escapedProcedureCallWithResult_ and all code
that is only executed
[ http://issues.apache.org/jira/browse/DERBY-1956?page=all ]
Knut Anders Hatlen updated DERBY-1956:
--
Derby Info: [Patch Available]
Remove stale code from the statement classes in the client driver
Factor out run-time statistics information from language ResultSet classes
--
Key: DERBY-1957
URL: http://issues.apache.org/jira/browse/DERBY-1957
Project: Derby
Issue
[
http://issues.apache.org/jira/browse/DERBY-1956?page=comments#action_12441775 ]
Knut Anders Hatlen commented on DERBY-1956:
---
It seems to be there to support a different parameter mapping for statements of
this kind:
[ http://issues.apache.org/jira/browse/DERBY-1956?page=all ]
Knut Anders Hatlen closed DERBY-1956.
-
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks Bryan and Dan for the comments. Committed revision 463565.
Remove stale code
[ http://issues.apache.org/jira/browse/DERBY-989?page=all ]
Knut Anders Hatlen reopened DERBY-989:
--
unit/daemonService.unit fails intermittently: 'ran out of time'
---
[ http://issues.apache.org/jira/browse/DERBY-989?page=all ]
Knut Anders Hatlen closed DERBY-989.
Fix Version/s: 10.1.3.2
Resolution: Fixed
Patch merged cleanly from trunk. Test passes. Committed into 10.1 with revision
463899.
[
http://issues.apache.org/jira/browse/DERBY-1895?page=comments#action_12442521 ]
Knut Anders Hatlen commented on DERBY-1895:
---
Hi Fernanda. Thank you for rewriting the test! I had a quick look at your patch
and the description of it.
Investigate resource usage for different types of load on an in-memory database
---
Key: DERBY-1961
URL: http://issues.apache.org/jira/browse/DERBY-1961
Project: Derby
[ http://issues.apache.org/jira/browse/DERBY-1883?page=all ]
Knut Anders Hatlen reopened DERBY-1883:
---
I18N tests fail on Linux/JVM 1.4.2 when derbyclient.jar is the first element
of the classpath
[ http://issues.apache.org/jira/browse/DERBY-1961?page=all ]
Knut Anders Hatlen updated DERBY-1961:
--
Attachment: TestClient.java
Uploaded a test client which can be used to investigate the resource
usage for three different loads:
-
[
http://issues.apache.org/jira/browse/DERBY-1961?page=comments#action_12442566 ]
Knut Anders Hatlen commented on DERBY-1961:
---
Created wiki page where results could be posted:
http://wiki.apache.org/db-derby/Derby1961ResourceUsage
[
http://issues.apache.org/jira/browse/DERBY-1893?page=comments#action_12442681 ]
Knut Anders Hatlen commented on DERBY-1893:
---
I have two comments to the patch (sorry I didn't notice before it was
committed):
- the suite method
[
http://issues.apache.org/jira/browse/DERBY-1962?page=comments#action_12442815 ]
Knut Anders Hatlen commented on DERBY-1962:
---
I think the patch looks good, but it seems the preferred way to make an
embedded-only suite has changed to
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12443040 ]
Knut Anders Hatlen commented on DERBY-801:
--
I'm wondering whether we should change the DEBUG_PRINT calls to
ASSERT/THROWASSERT. Falling back to the old
[
http://issues.apache.org/jira/browse/DERBY-1965?page=comments#action_12443046 ]
Knut Anders Hatlen commented on DERBY-1965:
---
I'm not sure that's the best use of try/finally. Take this code for example:
try {
setUpSocket();
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12443179 ]
Knut Anders Hatlen commented on DERBY-801:
--
Army Brown reported an intermittent assert failure in a comment to DERBY-1976.
It is probably related to this
[ http://issues.apache.org/jira/browse/DERBY-1895?page=all ]
Knut Anders Hatlen resolved DERBY-1895.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks Fernanda. Committed revision 465601.
[ http://issues.apache.org/jira/browse/DERBY-1918?page=all ]
Knut Anders Hatlen resolved DERBY-1918.
---
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed revision 465615.
INCREMENT of IDENTITY column described as allowing a
[ http://issues.apache.org/jira/browse/DERBY-1962?page=all ]
Knut Anders Hatlen resolved DERBY-1962.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed revision 465694.
Convert
[
http://issues.apache.org/jira/browse/DERBY-1978?page=comments#action_12443627 ]
Knut Anders Hatlen commented on DERBY-1978:
---
Is this the same as DERBY-912?
OutOfMemory error still happens in 10.2.1.6
[
http://issues.apache.org/jira/browse/DERBY-912?page=comments#action_12443644 ]
Knut Anders Hatlen commented on DERBY-912:
--
The problem seems to be that RAMTransaction.sorts is only cleared when the
connection is closed, not when the
[
http://issues.apache.org/jira/browse/DERBY-912?page=comments#action_12443651 ]
Knut Anders Hatlen commented on DERBY-912:
--
One simple solution is to remove all trailing null elements from the sorts
vector on commit. That should leave
[ http://issues.apache.org/jira/browse/DERBY-912?page=all ]
Knut Anders Hatlen reassigned DERBY-912:
Assignee: Knut Anders Hatlen
OutOfMemory error on continuous execution of SQL statement
[
http://issues.apache.org/jira/browse/DERBY-1912?page=comments#action_12443917 ]
Knut Anders Hatlen commented on DERBY-1912:
---
This issue sounds similar to DERBY-300. DERBY-300 reports hangs on 1.3 JVMs
when the client and the server
[ http://issues.apache.org/jira/browse/DERBY-912?page=all ]
Knut Anders Hatlen updated DERBY-912:
-
Attachment: derby-912.diff
Attaching a patch which implements reuse of sort identifiers, as suggested by
Mike.
I have successfully run the repro for
[ http://issues.apache.org/jira/browse/DERBY-912?page=all ]
Knut Anders Hatlen updated DERBY-912:
-
Derby Info: [Patch Available]
OutOfMemory error on continuous execution of SQL statement
--
Convert jdbc4/TestJDBC40Exception.java to JUnit
---
Key: DERBY-1988
URL: http://issues.apache.org/jira/browse/DERBY-1988
Project: Derby
Issue Type: Improvement
Components: Test
[ http://issues.apache.org/jira/browse/DERBY-1988?page=all ]
Knut Anders Hatlen updated DERBY-1988:
--
Attachment: exceptiontest.diff
exceptiontest.stat
The attached exceptiontest.diff converts TestJDBC40Exception to JUnit. Since
one
[ http://issues.apache.org/jira/browse/DERBY-1988?page=all ]
Knut Anders Hatlen updated DERBY-1988:
--
Derby Info: [Patch Available]
Convert jdbc4/TestJDBC40Exception.java to JUnit
---
Convert jdbc4/TestDbMetaData.java to JUnit
--
Key: DERBY-1989
URL: http://issues.apache.org/jira/browse/DERBY-1989
Project: Derby
Issue Type: Improvement
Components: Test
Affects
[ http://issues.apache.org/jira/browse/DERBY-1979?page=all ]
Knut Anders Hatlen resolved DERBY-1979.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
I was curious about why the test only ran in
[
http://issues.apache.org/jira/browse/DERBY-2017?page=comments#action_12445568 ]
Knut Anders Hatlen commented on DERBY-2017:
---
When this issue has been fixed, jdbcapi/CharacterStreamsTest should be updated
so that it runs with the
[ http://issues.apache.org/jira/browse/DERBY-1991?page=all ]
Knut Anders Hatlen closed DERBY-1991.
-
Fix Version/s: 10.2.1.8
10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed to trunk with
[ http://issues.apache.org/jira/browse/DERBY-1868?page=all ]
Knut Anders Hatlen updated DERBY-1868:
--
Attachment: antlib.diff
I'm not able to build Derby after these changes, probably because my ant
installation doesn't have ant.jar under
[ http://issues.apache.org/jira/browse/DERBY-2027?page=all ]
Knut Anders Hatlen resolved DERBY-2027.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks Kristian. Committed revision 470294.
[
http://issues.apache.org/jira/browse/DERBY-1961?page=comments#action_12446601 ]
Knut Anders Hatlen commented on DERBY-1961:
---
The wiki page disappeared and I was unable to restore it with the same name.
New location for the results:
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12446607 ]
Knut Anders Hatlen commented on DERBY-801:
--
I couldn't build the jar files with this patch because the build system
expected
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12446609 ]
Knut Anders Hatlen commented on DERBY-801:
--
if we agree that closing a container that is being dropped while IO is still
active on it is sane, it
Convert derbynet/testProtocol.java to JUnit
---
Key: DERBY-2031
URL: http://issues.apache.org/jira/browse/DERBY-2031
Project: Derby
Issue Type: Improvement
Components: Network Server, Test
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12446767 ]
Knut Anders Hatlen commented on DERBY-801:
--
Thanks Anders. I committed DERBY-801-6.patch with revision 470573.
I'm not sure checking for the committed
lang/releaseCompileLocks.sql and lang/closed.java fail under JDK 1.6 in insane
mode
---
Key: DERBY-2038
URL: http://issues.apache.org/jira/browse/DERBY-2038
Project:
[ http://issues.apache.org/jira/browse/DERBY-801?page=all ]
Knut Anders Hatlen updated DERBY-801:
-
Derby Info: (was: [Patch Available])
Allow parallel access to data files.
Key: DERBY-801
Make class org.apache.derby.iapi.store.raw.PageKey final
Key: DERBY-2046
URL: http://issues.apache.org/jira/browse/DERBY-2046
Project: Derby
Issue Type: Improvement
TestDataSourceFactory doesn't work correctly outside the old harness
Key: DERBY-2047
URL: http://issues.apache.org/jira/browse/DERBY-2047
Project: Derby
Issue Type: Bug
[ http://issues.apache.org/jira/browse/DERBY-2047?page=all ]
Knut Anders Hatlen reassigned DERBY-2047:
-
Assignee: Knut Anders Hatlen
TestDataSourceFactory doesn't work correctly outside the old harness
[ http://issues.apache.org/jira/browse/DERBY-2047?page=all ]
Knut Anders Hatlen updated DERBY-2047:
--
Attachment: derby-2047.diff
derby-2047.stat
The attached patch (derby-2047.diff) makes TestDataSourceFactory
independent of
[ http://issues.apache.org/jira/browse/DERBY-2023?page=all ]
Knut Anders Hatlen reassigned DERBY-2023:
-
Assignee: Knut Anders Hatlen
Ensure all tests called by jdbc40._Suite run in embedded and client as
required.
[ http://issues.apache.org/jira/browse/DERBY-2023?page=all ]
Knut Anders Hatlen updated DERBY-2023:
--
Attachment: derby-2023.diff
derby-2023.stat
The attached patch (derby-2023.diff) makes most of the tests in
jdbc4._Suite run in
[ http://issues.apache.org/jira/browse/DERBY-2023?page=all ]
Knut Anders Hatlen updated DERBY-2023:
--
Derby Info: [Patch Available]
Ensure all tests called by jdbc40._Suite run in embedded and client as
required.
[
http://issues.apache.org/jira/browse/DERBY-2047?page=comments#action_12447484 ]
Knut Anders Hatlen commented on DERBY-2047:
---
Thanks Dan, I hadn't noticed your comment about this problem under DERBY-2043.
Your approach sounds cleaner
901 - 1000 of 8954 matches
Mail list logo