Rick said for 10.2 we could use the Fix Version on unassigned issues to
mark high value fix candidates for the release and then iteratively
adjust the list as individual issues look like could not be fixed by the
fix date.
Long gone are the days where I knew every significant bug personally
[
http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12423780 ]
V.Narayanan commented on DERBY-694:
---
The following test cases would test the patch in greater detail
1) Generate a case which will cause a ABNUOWRM that will caus
[ http://issues.apache.org/jira/browse/DERBY-1363?page=all ]
Kathey Marsden updated DERBY-1363:
--
Fix Version/s: 10.2.0.0
Setting this to fix version 10.2 as a high value fix candidate. This issue
has hit virtually every new developer that has joined
[
http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12423772 ]
Yip Ng commented on DERBY-1543:
---
Are you referring in the context of Derby? For example, DB2 and IDS allows
synonyms in their GRANT or REVOKE statements.
db2 => cr
[ http://issues.apache.org/jira/browse/DERBY-1275?page=all ]
Kathey Marsden updated DERBY-1275:
--
Fix Version/s: 10.2.0.0
Adding this as a high value fix candidate to the 10.2 list so that it might be
picked up for 10.2. The original crisis that prompt
[ http://issues.apache.org/jira/browse/DERBY-1562?page=all ]
Kathey Marsden updated DERBY-1562:
--
Component/s: Test
> Have BaseJDBCTestCase have a Connection field to cover the common case where
> one connection is used.
> --
[ http://issues.apache.org/jira/browse/DERBY-1585?page=all ]
Kathey Marsden updated DERBY-1585:
--
Component/s: Test
Description:
* Diff file derbyall/derbylang/procedureInTrigger.diff
*** Start: procedureInTrigger jdk1.6.0-rc derbyall:derbyla
[
http://issues.apache.org/jira/browse/DERBY-1543?page=comments#action_12423757 ]
Satheesh Bandaram commented on DERBY-1543:
--
What is the failure you are seeing with synonyms? Attempting to GRANT or REVOKE
privileges to synonyms should
[ http://issues.apache.org/jira/browse/DERBY-1574?page=all ]
Dag H. Wanvik updated DERBY-1574:
-
Attachment: predicatePushdown.diff
derby1574.diff
I looked at it out of curiosity (I am not very familiar with this part
of the code); it seem
Hi,
I ran into the following interesting situation with permissions
granted as per derby_tests.policy, and I'm hoping someone can answer
my questions:
- start networkserver with derby_tests.policy as described in the
remote server testing section of the java/testing/README.htm, but with
-h
- sta
I was also wondering if a bug with a higher number of votes should be
taken to be more severe. Or having higher priority?
Myrna
[ http://issues.apache.org/jira/browse/DERBY-1592?page=all ]
Satheesh Bandaram closed DERBY-1592.
Assignee: Satheesh Bandaram
> Update statement is allowed to execute even though the column that the
> statement access has been revoked.
> ---
[ http://issues.apache.org/jira/browse/DERBY-1592?page=all ]
Satheesh Bandaram resolved DERBY-1592.
--
Resolution: Invalid
Reporter of this defect agreed this is expected behavior. I will update
functional spec to cover this issue, so it becomes clea
On 7/26/06, Kathey Marsden <[EMAIL PROTECTED]> wrote:
I agree. If a JIRA admin can enable the urgency field then the community
can start marking urgency for the 10.2 issues as they think appropriate
without regard to JIRA Priority (severity)/ The release manager, The
reporter, the assignee, or
[
http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12423744 ]
Satheesh Bandaram commented on DERBY-1521:
--
I seem to have missed one of Dan's questions about GRANT & REVOKE in this entry:
"
* Add basic tests to test g
[
http://issues.apache.org/jira/browse/DERBY-939?page=comments#action_12423743 ]
A B commented on DERBY-939:
---
Review comments can be found here:
http://article.gmane.org/gmane.comp.apache.db.derby.devel/24721
> NullPointerException at ResultSet.clo
[
http://issues.apache.org/jira/browse/DERBY-883?page=comments#action_12423742 ]
A B commented on DERBY-883:
---
Review comments incorporated into version 3 and 4 patches can be found here:
http://article.gmane.org/gmane.comp.apache.db.derby.devel/2448
Yip Ng (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-939?page=all ]
Yip Ng updated DERBY-939:
-
Attachment: derby939trunkdiffpatch1.txt
derby939trunkstatpatch1.txt
Here is the patch for DERBY-939.
I have reviewed the patch and t
Daniel John Debrunner wrote:
I see what you mean, even though there is no "transition from the
current scheme". We don't have a current scheme for defining
priority(jira urgency), only one for defining severity(jira priority).
I agree. If a JIRA admin can enable the urgency field then the co
Scripts in frameworks direcotry needs to be revisted to set up CLASSPATH
properly
-
Key: DERBY-1597
URL: http://issues.apache.org/jira/browse/DERBY-1597
Project: Derby
[
http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12423730 ]
Deepa Remesh commented on DERBY-1521:
-
Thanks Dan for looking at patch1.
Answers to Dan's concerns:
1) In the next patch I am working on, I will change
"tes
[ http://issues.apache.org/jira/browse/DERBY-1521?page=all ]
Daniel John Debrunner updated DERBY-1521:
-
Derby Info: (was: [Patch Available])
Patch Committed revision 425846.
Two issues to be addressed though:
1) The code that calls testGrantR
Kathey Marsden wrote:
...
> 3) We need to decide what to do about the password. On IRC andersmo
> mentioned really anyone can have it sent to the list by pressing the
> send me my password button. Perhaps we can find out how Forrest handles
> it.
I found a post in the forrest archives [1] that m
Rick Hillegas wrote:
> I'm simply trying to clarify the transition from the current scheme to
> Kathey's preferred scheme. Someone has to fill in the value of Urgency
> for pre-existing issues. I'm asking whether this is the algorithm for
> determining Urgency values for 10.2 issues which have alr
Hi Kathey,
I think we're on the same page. I hope my reply to Dan's question
clarified the intention of my mapping table. I'm trying to figure out
how we assign Urgency values to existing 10.2 JIRAs. I'm asking whether
this is the algorithm you would use.
At the risk of being pedantic and cr
I created a derby-dev JIRA account so we can get weekly patch list
notification. But there are few outstanding issues.
1) derby-dev needs JIRA developer access so it can subscribe to the
patch report
2) [EMAIL PROTECTED] needs to subscribe to the derby-dev developer list
so the patch report
Daniel John Debrunner wrote:
Rick Hillegas wrote:
Thanks, Kathey. I think this does capture what I mean. I think this is
your proposal:
Priority - Means "severity" according to the JIRA definitions.
Urgency - Has the common-sense meaning of priority, not to be confused
with the JIRA sense
Rick Hillegas wrote:
Thanks, Kathey. I think this does capture what I mean. I think this is
your proposal:
Priority - Means "severity" according to the JIRA definitions.
Urgency - Has the common-sense meaning of priority, not to be confused
with the JIRA sense.
Yes, that makes sense , but
Rick Hillegas wrote:
> Thanks, Kathey. I think this does capture what I mean. I think this is
> your proposal:
>
> Priority - Means "severity" according to the JIRA definitions.
>
> Urgency - Has the common-sense meaning of priority, not to be confused
> with the JIRA sense.
>
> For current 10.
Thanks, Kathey. I think this does capture what I mean. I think this is
your proposal:
Priority - Means "severity" according to the JIRA definitions.
Urgency - Has the common-sense meaning of priority, not to be confused
with the JIRA sense.
For current 10.2 issues:
Priority==Blocker => Urge
Hi Manish,
Thanks for addressing my comments. The patch is looking better now--especially
with the whitespace issues in version 4. Some follow-up comments below.
Manish Khettry wrote:
>> 1) TernarnyOpNode.isEquivalent(): I think we need to check "receiver"
>> equivalence as well, in additio
[
http://issues.apache.org/jira/browse/DERBY-1544?page=comments#action_12423717 ]
Satheesh Bandaram commented on DERBY-1544:
--
Changes to update database owner is already present in Derby upgrade
process it seems there is a defect th
Rick Hillegas wrote:
How is this field used? Does it take two values (Urgent, NotUrgent) or
does it cover a broader spectrum?
Here is the forrest definition, which looks closely correlated with
with what we are trying to achieve.
If I had my druthers I would alter Urgent a bit to include
[ http://issues.apache.org/jira/browse/DERBY-1456?page=all ]
Sunitha Kambhampati updated DERBY-1456:
---
Assignee: Sunitha Kambhampati
Derby Info: [Patch Available]
> Network Server agentError calls log only to console and are hard to diagnose
>
[ http://issues.apache.org/jira/browse/DERBY-1456?page=all ]
Sunitha Kambhampati updated DERBY-1456:
---
Attachment: derby1456.diff.txt
derby1456.stat.txt
1456_notes.txt
I am attaching a patch 'derby1456.diff.txt' and t
[ http://issues.apache.org/jira/browse/DERBY-883?page=all ]
Manish Khettry updated DERBY-883:
-
Attachment: 883.patch4.txt
I found a problem in one of my changes. Also got rid of a lot of white space
only diffs.
> Enhance GROUP BY clause to support exp
[ http://issues.apache.org/jira/browse/DERBY-1539?page=all ]
Daniel John Debrunner updated DERBY-1539:
-
Derby Info: (was: [Patch Available])
Patch DERBY1539V4diffDropTriggerOnRevoke.txt Committed revision 425836
> As per the functional spec at
Myrna van Lunteren wrote:
Hi,
I have a question on the commit.
You added permissions for localhost and 127.0.0.1, i.e. also localhost...
I think this means this problem might then still pop up in remote
server testing, no?
I don't understand the nature of the problem...but I think this means
th
[
http://issues.apache.org/jira/browse/DERBY-1521?page=comments#action_12423709 ]
Deepa Remesh commented on DERBY-1521:
-
For Dan's question: I think this is planned to be covered by DERBY-1544.
> Upgrade test needs to be enhanced to test gra
Daniel John Debrunner wrote:
Rick Hillegas wrote:
For 10.2, I want to use the priority field to mean what it means in
other bug tracking systems: a field which helps engineers figure out
what to do next. I would appreciate it if people would use Blocker and
Critical to mean, respectively, "
[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ]
Deepa Remesh updated DERBY-1130:
Derby Info: (was: [Patch Available])
> Client should not allow databaseName to be set with setConnectionAttributes
> -
Hi Kathey,
How is this field used? Does it take two values (Urgent, NotUrgent) or
does it cover a broader spectrum? This might help us separate the
concepts of priority and severity. However, I think there will continue
to be confusion as long as a field named "priority" is used to hold the
c
[ http://issues.apache.org/jira/browse/DERBY-1030?page=all ]
Mamta A. Satoor reassigned DERBY-1030:
--
Assignee: (was: Mamta A. Satoor)
Busy with grant revoke work, so unassigning myself from this one.
> In some situations a RETURNS NULL ON NULL
Rick Hillegas wrote:
> For 10.2, I want to use the priority field to mean what it means in
> other bug tracking systems: a field which helps engineers figure out
> what to do next. I would appreciate it if people would use Blocker and
> Critical to mean, respectively, "priority 1" and "priority 2"
Rick Hillegas wrote:
Hi Kathey,
I think that this is a defect in JIRA. If someone knows how to add a
severity field to our bug tracker, that would be great.
I notice when I take a Jira report there is an URGENCY option, under
custom fields with:
Blocker
Urgent
Normal
Low
But
Kathey Marsden wrote:
Rick Hillegas wrote:
. I would appreciate it if people would use Blocker and Critical to
mean, respectively, "priority 1" and "priority 2".
Can you put some words around "Priority 1" and "Priority 2" so I have
a better understanding of where to draw the line?
How'
Rick Hillegas wrote:
. I would appreciate it if people would use Blocker and Critical to
mean, respectively, "priority 1" and "priority 2".
Can you put some words around "Priority 1" and "Priority 2" so I have a
better understanding of where to draw the line?
Hi Kathey,
I agree that this is a bit confusing. In other bug tracking systems
which I have used, there is a distinction between the priority and the
severity of a bug. Priority is the field which helps engineers figure
out which bug to tackle next. Severity captures the bug's impact on
custo
*** (LS) I spoke offline with Eric and we decided that I should take
over documenting this feature for 10.2.
On 7/26/06, Laura Stewart (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1057?page=all ]
Laura Stewart reassigned DERBY-1057:
As
[
http://issues.apache.org/jira/browse/DERBY-765?page=comments#action_12423690 ]
Rick Hillegas commented on DERBY-765:
-
Re-entering the release note to correct a problem with the previous version,
found by Army.
Here's a release note for t
[ http://issues.apache.org/jira/browse/DERBY-1057?page=all ]
Laura Stewart reassigned DERBY-1057:
Assignee: Laura Stewart (was: Eric Radzinski)
> documentation to address Grant/Revoke (Derby-464)
> -
>
Hi Army,
Thanks for catching this. No, you're not missing anything. I was
experimenting with problem queries and didn't correct this one.
Thanks,
-Rick
Army wrote:
Rick Hillegas (JIRA) wrote:
WORKAROUND:
You can work around this limitation by rewriting your query so that
the SELECT list
Rick Hillegas wrote:
Hi Kathey,
If an issue would cause you to vote -1 on the 10.2 release, please
mark the issue as Critical or Blocker.
I am looking now at the known open regressions and am still struggling
with how to set the priority. Here is the current list of 4.
https://issues.apa
Rick Hillegas (JIRA) wrote:
WORKAROUND:
You can work around this limitation by rewriting your query
so that the SELECT list does not alias an expression to the
same name as another column or alias. The following rewritten
query works fine:
select a+1 as a, a+1 as c from myTable group by b;
Hello Kristian.
Thank you for taking my second opinion into account :)
I think EncodedInputStream is much better than before,
UTF32BEEncodedInputStream.
Best regards.
Kristian Waagan (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ]
Kristian Waagan updated DERB
Hi,
I was going through the grant revoke functional spec which is attached to DERBY-464 and was puzzled by following example in there
CREATE VIEW s.v(vc1,vc2,vc3) AS SELECT t1.c1,t1.c2,f(t1.c3) FROM t1 JOIN t2 ON t1.c1 = t2.c1 WHERE t2.c2 = 5
Jane needs the following permissions in order
[
http://issues.apache.org/jira/browse/DERBY-765?page=comments#action_12423684 ]
Rick Hillegas commented on DERBY-765:
-
Here's a release note for this issue:
PROBLEM
Derby raises an error for queries with the following profile:
o The query
Add demo programs needed for Working With Derby activities to the Derby
codeline and build: WwdEmbedded.java, WwdClient.java and WwdUtils.java
--
[
http://issues.apache.org/jira/browse/DERBY-1592?page=comments#action_12423683 ]
Yip Ng commented on DERBY-1592:
---
Right, there is a syntactical difference comparing to DB2's revoke statement
where it does not take privilege column list.
>From loo
[ http://issues.apache.org/jira/browse/DERBY-765?page=all ]
Kathey Marsden updated DERBY-765:
-
Derby Info: [Existing Application Impact, Regression, Release Note Needed]
This is a regression introduced by the fix for DERBY-280. After some
discussion on
[
http://issues.apache.org/jira/browse/DERBY-1592?page=comments#action_12423680 ]
Satheesh Bandaram commented on DERBY-1592:
--
This functionality is not supported. If a table level privilege has been
granted, revoking part of that privil
Hi,
I have a question on the commit.
You added permissions for localhost and 127.0.0.1, i.e. also localhost...
I think this means this problem might then still pop up in remote
server testing, no?
I don't understand the nature of the problem...but I think this means
that a similar permission nee
[ http://issues.apache.org/jira/browse/DERBY-1540?page=all ]
Rick Hillegas closed DERBY-1540.
Resolution: Fixed
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> -
[ http://issues.apache.org/jira/browse/DERBY-1540?page=all ]
Rick Hillegas updated DERBY-1540:
-
Attachment: derby-1540_v01.diff
This was a bug in the Mustang beta, which has been fixed. The attached patch
(derby-1540_v01.diff) causes this test to run un
[ http://issues.apache.org/jira/browse/DERBY-1541?page=all ]
Rick Hillegas reassigned DERBY-1541:
Assignee: Rick Hillegas
> Make test jdbc4/TestPreparedStatement run under the security manager
> ---
[ http://issues.apache.org/jira/browse/DERBY-1540?page=all ]
Rick Hillegas reassigned DERBY-1540:
Assignee: Rick Hillegas
> JDBC 4 EoD with default QueryObjectGenerator fails with SecurityManager
> ---
[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ]
Kristian Waagan updated DERBY-1417:
---
Attachment: derby-1417-6c-clientimpl.diff
'derby-1417-6c-clientimpl.diff' deprecates 6b.
Added both size of the character buffer and the initial size of t
[ http://issues.apache.org/jira/browse/DERBY-1541?page=all ]
Rick Hillegas closed DERBY-1541.
Resolution: Fixed
> Make test jdbc4/TestPreparedStatement run under the security manager
>
[ http://issues.apache.org/jira/browse/DERBY-1541?page=all ]
Rick Hillegas updated DERBY-1541:
-
Attachment: derby-1541_v01.diff
This file is a piece of cruft which is not used by any test. The live tests
were moved into TestPreparedStatementMethods, and
[
http://issues.apache.org/jira/browse/DERBY-1546?page=comments#action_12423667 ]
Rick Hillegas commented on DERBY-1546:
--
Hi Knut Anders. Thanks for the ample explanation of the changes. They look good
to me.
> Derby JDBC 4.0 driver return
TomohitoNakayama wrote:
Hello Kristian.
Thank you for taking my consideration into the patch and fix failure in
the name of class !
One more my opinion
In some encodings, such as UTF-16 "with Byte Order Mark" or ISO-2022-JP,
length of encoded bytes array is not just multiple of character
[ http://issues.apache.org/jira/browse/DERBY-1546?page=all ]
Knut Anders Hatlen updated DERBY-1546:
--
Derby Info: [Patch Available]
> Derby JDBC 4.0 driver returns 3 for JDBC driver major version
>
[ http://issues.apache.org/jira/browse/DERBY-1546?page=all ]
Knut Anders Hatlen updated DERBY-1546:
--
Attachment: derby-1546-v1.diff
derby-1546-v1.stat
derby-1546-v1.diff makes getJDBCMajorVersion() return 4 when using the
JDBC 4.0 dr
[ http://issues.apache.org/jira/browse/DERBY-464?page=all ]
Mamta A. Satoor updated DERBY-464:
--
I think I accidentally selected patch available when I attached the updated
fucntional spec.
> Enhance Derby by adding grant/revoke support. Grant/Revoke provi
Thanks, Suresh. I have attached corresponding documentation to DERBY-1594.
Regards,
-Rick
Suresh Thalamati wrote:
Rick Hillegas wrote:
GRANT/REVOKE requires catalog support and so won't be available to
users who soft-upgrade to 10.2. Are there other 10.2 features which
will not be availabl
[ http://issues.apache.org/jira/browse/DERBY-1594?page=all ]
Rick Hillegas updated DERBY-1594:
-
Derby Info: [Patch Available]
> List other 10.2 features which will not be available after soft upgrade.
> ---
[ http://issues.apache.org/jira/browse/DERBY-1594?page=all ]
Rick Hillegas updated DERBY-1594:
-
Attachment: derby-1594_v01.diff
devguide.tar.gz
Attaching patch derby-1594_v01.diff and gzip of corresponding html/pdf output
for the Develop
Yuck. OK, I'll work on these. Next time someone creates a request to
change code that affects the output of master files, I'm going to run
screaming to the hills... :)
David
Kristian Waagan (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1578?page=comments#action_12423631 ]
[ http://issues.apache.org/jira/browse/DERBY-464?page=all ]
Daniel John Debrunner updated DERBY-464:
Derby Info: (was: [Patch Available])
Don't see any patch that hasn't been committed.
> Enhance Derby by adding grant/revoke support. Grant/Rev
[ http://issues.apache.org/jira/browse/DERBY-1539?page=all ]
Mamta A. Satoor updated DERBY-1539:
---
Attachment: DERBY1539V4diffDropTriggerOnRevoke.txt
Sorry about the mix up. This is what I get for staying up late.
I have attached the patch as DERBY1539
Network server fails with DRDAProtocolException if a BLOB with size 2147483647
is streamed from client
--
Key: DERBY-1595
URL: http://issues.apache.org/jira/browse
[ http://issues.apache.org/jira/browse/DERBY-551?page=all ]
Daniel John Debrunner updated DERBY-551:
Derby Info: (was: [Patch Available])
> Allow invoking java stored procedures from inside a trigger. Make CALL a
> valid statement in the trigg
[Auto-generated mail]
*TinderBox_Derby* 425703/2006-07-26 13:13:04 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1680679 2 145.68% SunOS-5.10_i86pc-i386
Details in
http://www.mult
Hello Kristian.
Thank you for taking my consideration into the patch and fix failure in
the name of class !
One more my opinion
In some encodings, such as UTF-16 "with Byte Order Mark" or ISO-2022-JP,
length of encoded bytes array is not just multiple of characters count.
In those cases,
[ http://issues.apache.org/jira/browse/DERBY-1594?page=all ]
Rick Hillegas updated DERBY-1594:
-
Fix Version/s: 10.2.0.0
Affects Version/s: 10.2.0.0
> List other 10.2 features which will not be available after soft upgrade.
> -
List other 10.2 features which will not be available after soft upgrade.
Key: DERBY-1594
URL: http://issues.apache.org/jira/browse/DERBY-1594
Project: Derby
Issue Type:
[ http://issues.apache.org/jira/browse/DERBY-1594?page=all ]
Rick Hillegas reassigned DERBY-1594:
Assignee: Rick Hillegas
> List other 10.2 features which will not be available after soft upgrade.
> ---
Separate test jar files from the "product" jars in a distribution
-
Key: DERBY-1593
URL: http://issues.apache.org/jira/browse/DERBY-1593
Project: Derby
Issue Type: Improvement
[
http://issues.apache.org/jira/browse/DERBY-1539?page=comments#action_12423648 ]
Daniel John Debrunner commented on DERBY-1539:
--
Mamta wrote:
2)I have moved the drop trigger code into makeInvalid call.
The v3 patch still has the
[ http://issues.apache.org/jira/browse/DERBY-1545?page=all ]
Andreas Korneliussen closed DERBY-1545.
---
> derbynet/testProtocol.java fails with security manager enabled
> --
>
>
[ http://issues.apache.org/jira/browse/DERBY-1545?page=all ]
Andreas Korneliussen resolved DERBY-1545.
-
Fix Version/s: 10.2.0.0
Resolution: Fixed
Committed revision 425732.
> derbynet/testProtocol.java fails with security manager enabled
[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ]
Kristian Waagan updated DERBY-1417:
---
Attachment: derby-1417-6b-clientimpl.diff
'derby-1417-6b-clientimpl.diff' deprecates 6a.
Changes:
1) Add missing license to two files.
2) Added static f
[ http://issues.apache.org/jira/browse/DERBY-936?page=all ]
Rick Hillegas closed DERBY-936.
---
Resolution: Fixed
> Main branch docs display version as 10.1, should be 10.2.
> -
>
> Key:
[
http://issues.apache.org/jira/browse/DERBY-936?page=comments#action_12423640 ]
Rick Hillegas commented on DERBY-936:
-
Thanks for the quick review, Andrew. Committed at subversion revision 425729.
> Main branch docs display version as 10.1,
Thanks, Jean. I wasn't around then. Who took part in those original
discussions?
Regards,
-Rick
Jean T. Anderson wrote:
Rick Hillegas wrote:
Thanks, Andrew!
Hi David and Jean,
Do either of you plan to broach with legal-discuss the issues raised by
DERBY-1377?
I think the ones who
[ http://issues.apache.org/jira/browse/DERBY-1587?page=all ]
Andreas Korneliussen resolved DERBY-1587.
-
Fix Version/s: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks for contributing.
Committed revision 42
[ http://issues.apache.org/jira/browse/DERBY-1563?page=all ]
Fernanda Pizzorno closed DERBY-1563.
> derbynet/ShutDownDBWhenNSShutsDownTest.junit fails on Solaris sparc
> ---
>
>
[
http://issues.apache.org/jira/browse/DERBY-1578?page=comments#action_12423631 ]
Kristian Waagan commented on DERBY-1578:
Here's a list of candidates :)
lang/compressTable.sql
lang/nestedCommit.sql
lang/outparams.java
lang/procedure.jav
[ http://issues.apache.org/jira/browse/DERBY-1563?page=all ]
Knut Anders Hatlen resolved DERBY-1563.
---
Resolution: Fixed
Thanks for fixing the test, Fernanda! Committed revision 425719.
> derbynet/ShutDownDBWhenNSShutsDownTest.junit fails on Solari
[ http://issues.apache.org/jira/browse/DERBY-1563?page=all ]
Fernanda Pizzorno updated DERBY-1563:
-
Attachment: derby-1563.diff
derby-1563.stat
The attached patch (derby-1563.diff) fixes the problem by waiting before
checking if the
1 - 100 of 125 matches
Mail list logo
