[ http://issues.apache.org/jira/browse/DERBY-1165?page=all ]
Knut Anders Hatlen closed DERBY-1165.
-
Resolution: Won't Fix
A test checking the transaction ids returned by xa_recover is needed
[
http://issues.apache.org/jira/browse/DERBY-1671?page=comments#action_12458387 ]
John H. Embretsen commented on DERBY-1671:
--
I am not a lawyer, but it sounds good to me... Are you aiming for JUnit 3.8.2?
Include junit.jar in Derby's
OutOfMemoryError in Network Server after running DOTS-like test for weeks
-
Key: DERBY-2176
URL: http://issues.apache.org/jira/browse/DERBY-2176
Project: Derby
Issue
Hello.
I think an efforts for readability of code came to improve stability of
code.
Please read next patch and give me your opinion.
Best regards.
Knut Anders Hatlen wrote:
TomohitoNakayama [EMAIL PROTECTED] writes:
Hello.
Knut Anders Hatlen (JIRA) wrote:
[...]
if
[ http://issues.apache.org/jira/browse/DERBY-1471?page=all ]
Tomohito Nakayama updated DERBY-1471:
-
Attachment: DERBY-1471_5.patch
DERBY-1471_5.status
* Description of the patch
* This patch implements Layer B streaming for new
[ http://issues.apache.org/jira/browse/DERBY-2107?page=all ]
Knut Anders Hatlen updated DERBY-2107:
--
Attachment: derby-2107-1b.diff
Attaching a new version of the patch to address Dan's comments. (Improved
synchronization and comments.)
If this
Dag H. Wanvik (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12458129 ]
Dag H. Wanvik commented on DERBY-2109:
--
Øystein:
I miss a rationale for how you ended up with three
database-specific features.
[
http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12458486 ]
Knut Anders Hatlen commented on DERBY-1471:
---
Thank you, Tomohito! The changes look good to me. I have verified that the
latest patch works with a new
[ http://issues.apache.org/jira/browse/DERBY-2176?page=all ]
John H. Embretsen updated DERBY-2176:
-
Attachment: derby.log
OU_jstat-gc-t.png
jmap-histo_server_17Nov1020CET.txt
Attached the following files, to help
[
http://issues.apache.org/jira/browse/DERBY-2175?page=comments#action_12458508 ]
Daniel John Debrunner commented on DERBY-2175:
--
Would it work if the list of exported packages was limited to the packages in
Derby's public api?
[
http://issues.apache.org/jira/browse/DERBY-2175?page=comments#action_12458510 ]
Nicolas Richeton commented on DERBY-2175:
-
Yes, only the public api should be exported, sorry.
I think the problem comes from the webstart classloader,
Issue Subscription
Filter: Derby: JIRA issues with patch available (11 issues)
Subscriber: derby-dev
Key Summary
DERBY-1471 Implement layer B streaming for new methods defined in JDBC4.0
http://issues.apache.org/jira/browse/DERBY-1471
DERBY-2107 Move page latching out of
[ http://issues.apache.org/jira/browse/DERBY-2176?page=all ]
John H. Embretsen updated DERBY-2176:
-
Attachment: OU_jstat-gc-t.png
Attached new and correct OU_jstat-gc-t.png (previous was from a different test).
OutOfMemoryError in Network Server
[
http://issues.apache.org/jira/browse/DERBY-2176?page=comments#action_12458519 ]
Knut Anders Hatlen commented on DERBY-2176:
---
I'm just guessing here, but the histogram of objects seems similar to what I
would expect from DERBY-912,
[
http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12458530 ]
Øystein Grøvlen commented on DERBY-2109:
Rick Hillegas (JIRA) wrote:
[
http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12458313
[
http://issues.apache.org/jira/browse/DERBY-2176?page=comments#action_12458539 ]
John H. Embretsen commented on DERBY-2176:
--
Thank you Knut Anders, that is an interesting theory! And if it is correct, it
seems like the problem has
[Auto-generated mail]
*Daily* 486739/2006-12-13 18:00:25 MET
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.6*
lin
0517517 0 100.07% derbyall
064786478 0 155.87% suitesAll
sol
1
[
http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12458563 ]
Daniel John Debrunner commented on DERBY-2109:
--
3) Plugin scope. I think that you and Dan agree that plugin is a
database-specific, not a
[
http://issues.apache.org/jira/browse/DERBY-2169?page=comments#action_12458564 ]
Yip Ng commented on DERBY-2169:
---
Another behavior not mentioned in the current documentation of
syscs_util.syscs_compress_table and
[ http://issues.apache.org/jira/browse/DERBY-1795?page=all ]
Kim Haase closed DERBY-1795.
Thanks very much for this fix, Andrew. Sorry to take so long to close it.
Graphics not copied over for PDF and HTML-single manuals
[ http://issues.apache.org/jira/browse/DERBY-1796?page=all ]
Kim Haase closed DERBY-1796.
Belated thanks for this fix, Andrew.
Typo in Tuning Derby graphics file name causes problems
---
[
http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12458573 ]
Rick Hillegas commented on DERBY-2109:
--
I do not understand the need to qualify createDatabase privilege with a list of
databases which the user is allowed
[
http://issues.apache.org/jira/browse/DERBY-2109?page=comments#action_12458577 ]
Daniel John Debrunner commented on DERBY-2109:
--
The permission would not be the names of databases that one can create, but
instead locations where
[ http://issues.apache.org/jira/browse/DERBY-1717?page=all ]
Kim Haase closed DERBY-1717.
Working With Derby task file twwdactivity4.dita is invalid, results in
missing text
---
Rick Hillegas (JIRA) wrote:
2) Unfamiliar api. Oracle, DB2, Postgres, and MySQL all handle system
privileges in different ways. Picking one of these models would still result in
an api that's unfamiliar to many people. That said, these databases do tend to
use GRANT/REVOKE for system
I agree with David on this that policy files are painful.
David Van Couvering wrote:
Rick Hillegas (JIRA) wrote:
2) Unfamiliar api. Oracle, DB2, Postgres, and MySQL all handle system
privileges in different ways. Picking one of these models would still
result in an api that's unfamiliar
[
http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12458593 ]
Daniel John Debrunner commented on DERBY-2107:
--
Even though the parameters have changed for LockingPolicy.lockRecordForRead its
description has not,
For me on Solaris when run against the release candidate's jar files,
derbyall succeeded under jdk14. Under jdk16 derbyall ran cleanly except
for the intermittent test failure DERBY-1585 (I re-ran that test and it
succeeded). The JDBC4 test suite ran cleanly under jdk16. I have
verified the
[
http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12458608 ]
Mike Matrigali commented on DERBY-2107:
---
I am reviewing the changes, and do agree with Dan's comments. Have you thought
about the implecations of order
[
http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12458609 ]
Daniel John Debrunner commented on DERBY-2107:
--
I think the patch has a severe problem, here is code from
RowLocking3.lockRecordForRead (one of
[ http://issues.apache.org/jira/browse/DERBY-2107?page=all ]
Mike Matrigali updated DERBY-2107:
--
Dan is absolutely right about the unlatch() call. Once unlatch call is made
the page is free to be thrown out of the cache and be replaced by a different
[ http://issues.apache.org/jira/browse/DERBY-2107?page=all ]
Mike Matrigali updated DERBY-2107:
--
Dan, do you think the current code is actually allowing another thread to latch
the page while the lock is waiting? I used to think it did, but definitely
[
http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12458623 ]
Daniel John Debrunner commented on DERBY-2107:
--
This is how the page latching currently works in the case when the lock manager
releases its latch:
derbyall/derbyall.fail:tools/importExportThruIJ.sql fails on zOs with ibm15SR(3)
Key: DERBY-2177
URL: http://issues.apache.org/jira/browse/DERBY-2177
Project: Derby
derbyall/derbynetclientmats/derbynetmats.fail:derbynet/DerbyNetAutoStart.java
fails on zOs with ibm 15 (SR3)
Key: DERBY-2178
URL:
[
http://issues.apache.org/jira/browse/DERBY-2107?page=comments#action_12458628 ]
Daniel John Debrunner commented on DERBY-2107:
--
I think the patch hit this issue due to some existing confusion with naming in
the existing code.
Thanks, David and Lance, for elaborating on the usability issue raised
by Øystein: policy files can be tricky to work with.
It seems to me a sysadmin needs our system privileges because she wants
to prevent malicious shutdown (shutdownEngine privilege) and resource
hogging (createDatabase
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12458635 ]
Suresh Thalamati commented on DERBY-378:
related discussion on the derby-dev list:
[
http://issues.apache.org/jira/browse/DERBY-378?page=comments#action_12458636 ]
Suresh Thalamati commented on DERBY-378:
Import uses VTI to import data into a table from a file. Just found out
that derby does not support CLOB/BLOB
David Van Couvering wrote:
Rick Hillegas (JIRA) wrote:
2) Unfamiliar api. Oracle, DB2, Postgres, and MySQL all handle system
privileges in different ways. Picking one of these models would still
result in an api that's unfamiliar to many people. That said, these
databases do tend to use
[
http://issues.apache.org/jira/browse/DERBY-2177?page=comments#action_12458639 ]
Rajesh Kartha commented on DERBY-2177:
--
Can you also post which SQL statements are throwing this error.
[
http://issues.apache.org/jira/browse/DERBY-2178?page=comments#action_12458643 ]
Manjula Kutty commented on DERBY-2178:
--
The derby.log has the following stack trace
BEGIN SHUTDOWN ERROR STACK -
ERROR XSLAQ:
suites.All fails after revision 483606 with ibm15
-
Key: DERBY-2179
URL: http://issues.apache.org/jira/browse/DERBY-2179
Project: Derby
Issue Type: Bug
Environment: with ibm 1.5. jvm,
[ http://issues.apache.org/jira/browse/DERBY-2179?page=all ]
Myrna van Lunteren updated DERBY-2179:
--
Attachment: run.out
suites.All fails after revision 483606 with ibm15
-
Key:
[ http://issues.apache.org/jira/browse/DERBY-2179?page=all ]
Myrna van Lunteren updated DERBY-2179:
--
Fix Version/s: 10.3.0.0
suites.All fails after revision 483606 with ibm15
-
[ http://issues.apache.org/jira/browse/DERBY-2179?page=all ]
Myrna van Lunteren updated DERBY-2179:
--
Affects Version/s: 10.3.0.0
suites.All fails after revision 483606 with ibm15
-
[
http://issues.apache.org/jira/browse/DERBY-1644?page=comments#action_12458648 ]
Bryan Pendleton commented on DERBY-1644:
Committed d1644_combined_v3.diff to the trunk as revision 487414.
I haven't marked this issue resolved yet
I am having trouble getting everything set up to commit patches.
I feel like a dolt.
#1 - I finally found the config file under the following path.
C:\Documents and Settings\stewartl\Application Data\Subversion
But this can't be the correct file. Almost all of the rows are
commented out...
Test upgradeTests/Upgrade_10_1_10_2.java fails with the 10.1.3 jars during the
10.2.2 test run
--
Key: DERBY-2180
URL: http://issues.apache.org/jira/browse/DERBY-2180
I feel like a dolt.
Please don't! This is a complicated process, and it takes everybody
a while to get their system set up successfully.
#3 - Myrna commented and that you've got an environment variable
$SVN_EDITOR set to some editor accessible on your PATH. (to vi, for
example).
FWIW, I
Laura Stewart wrote:
I am having trouble getting everything set up to commit patches.
I feel like a dolt.
#1 - I finally found the config file under the following path.
C:\Documents and Settings\stewartl\Application Data\Subversion
But this can't be the correct file. Almost all of the
[ http://issues.apache.org/jira/browse/DERBY-2179?page=all ]
Daniel John Debrunner updated DERBY-2179:
-
Component/s: Test
Assignee: Daniel John Debrunner
Derby Info: (was: [Regression])
Thanks for the investigation Myrna, made it
52 matches
Mail list logo
