[Auto-generated mail]
*TinderBox_Derby* 414654/2006-06-15 20:53:04 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1673672 2 144.99% SunOS-5.10_i86pc-i386
Details in
Sunitha Kambhampati wrote:
But my point was to state that - irrespective of what a good value
for the client server is, the server's max query blocksize should be
10M ( which is per the spec).
I am sorry I have not followed this issue and thread closely but was
wondering. Does the max
1) In Working With Derby, Activity 1: Run SQL using the Embedded driver, is
written:
The DERBY_HOME variable defines the filesystem path to the root directory of
the Derby
installation.
set DERBY_HOME=C:\derby
2) In Derby Developer's Guide, The installation directory, is written:
The
But my point was to state that - irrespective of what a good value
for the client server is, the server's max query blocksize should be
10M ( which is per the spec). Does that sound reasonable to you ?
Yes, absolutely.
thanks,
bryan
From the tinderbox report it seems to have failed from the time the
following change was committed:
Changes from 414231/414413 to 414416:
r414416 | davidvc | 2006-06-15 02:00:44 +0200 (Thu, 15 Jun 2006) | 4 lines
Removed
*Good *write up! I am not a big fan of silently ignoring user specified
value, even if specified incorrectly. I would vote for filing a big to
correct two issues 1) Checking for less than Integer.MAX_VALUE value
after multiplying specified value by 1024 and 2) Raising an error for
negative values.
I ran derbyall on my machine prior to checkin and it worked. But this
checkin was the first time derbyall included MessageBundleTest. It did
not pass before then. I must have not properly checked in the output
file, is all I can think of. I'll look into this, apologies.
David
Mike
[ http://issues.apache.org/jira/browse/DERBY-578?page=all ]
Manish Khettry updated DERBY-578:
-
Attachment: predicatePushdown.out.patch
Looks like the join order changed between when I generated the patch and now.
Try this version of predicatePushdown.
Kathey Marsden wrote:
Does the max query blocksize affect the DDMReader buffer size?
Good question. I assume you meant the DDMWriter that has the send
buffer, initial size of 32767.
The max query blocksize is an upper bound on the query block size that
the server will accept. This
On 6/15/06, Mike Matrigali [EMAIL PROTECTED] wrote:
Note that this change is not as easy as it seems.I believe thereare all sorts of upgrade issues.I don't think it is possible tochange the name in 10.1 as 2 different versions of CS running indifferent jvms won't agree on the object they are
Manish Khettry (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-578?page=all ]
Manish Khettry updated DERBY-578:
-
Attachment: predicatePushdown.out.patch
Looks like the join order changed between when I generated the patch and now.
Try this
DERBY_INSTALL is what has been in place.
If I remember right, DERBY_HOME was to be introduced in 10.2 to conform
to the usage of other Apache projects. And I bet there's even a Jira
issue for that ... I'll post a followup when I find it (unless somebody
beats me to it).
-jean
Halley Pacheco de
--- Army [EMAIL PROTECTED] wrote:
Did your changes actually make it so that the query
no longer uses an index on
T1, or did it just change the logQueryPlan output so
that the index is no longer
being printed?
Actually, neither. The qeury plan was erroneusly
reporting an index being
Jean T. Anderson wrote:
DERBY_INSTALL is what has been in place.
If I remember right, DERBY_HOME was to be introduced in 10.2 to conform
to the usage of other Apache projects. And I bet there's even a Jira
issue for that ... I'll post a followup when I find it (unless somebody
beats me to
Manish Khettry wrote:
The qeury plan was erroneusly reporting an index being
used when none was being used. Try to do a distinct scan
on a table without an index.
-
maximumdisplaywidth 2;
create table noindex (x int);
call SYSCS_UTIL.SYSCS_SET_RUNTIMESTATISTICS(1);
select
I am looking at DERBY-989 and it would help to see the derby.log file
from the reported diff. I looked at the public web site:
http://www.multinet.no/~solberg/public/Apache/, but I could
only find reports on the results, not the actual results. I could very
well have missed something, and also
The maximum value is 2097151, which comes
from java.lang.Integer.MAX_VALUE / 1024.
Army, this is a *wonderful* writeup -- thank you very much?
Is it really realistic, though, to allow a setting of 2 million,
which gives the optimizer permission to try to create a
in-memory hash table of 2
Hi,
I noticed that Andrew had to recently make a checkin # 413411 because JitTest.java prints out Derby version, name and driver name. In order to make the test output independent of Derby releases, I have changed the test to not display Derby version specific info. The patch for that change is
[
http://issues.apache.org/jira/browse/DERBY-1409?page=comments#action_12416299 ]
Kristian Waagan commented on DERBY-1409:
Is this change required to run existing tests the way you want to, or are you
writing new tests?
I just want to point out
[
http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12416300 ]
Bernt M. Johnsen commented on DERBY-528:
At a first glance:
NetConnectionRequest.java has only whitespace changes and should not be part of
the patch.
There's a lot of
[Auto-generated mail]
*Derby* 414322/2006-06-14 19:46:07 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
15712697 0 106.69% SunOS-5.10_i86pc-i386
Details in
[ http://issues.apache.org/jira/browse/DERBY-137?page=all ]
Knut Anders Hatlen reassigned DERBY-137:
Assign To: Knut Anders Hatlen
Derby metadata always returns JDBC 2 result sets, even when JDBC 3 result
sets are required.
I intend to commit this patch unless someone protests within a day or
two.
Andreas Korneliussen (JIRA) wrote (2006-06-12 12:58:30):
[
http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415856
]
Andreas Korneliussen commented on DERBY-1384:
[
http://issues.apache.org/jira/browse/DERBY-1388?page=comments#action_12416319 ]
Tomohito Nakayama commented on DERBY-1388:
--
Sendingjava/client/org/apache/derby/client/net/Request.java
Adding
Is it possible to get some synergy between this project and ddl-utils?
(See http://db.apache.org/derby/integrate/db_ddlutils.html)
Apache Wiki wrote (2006-06-01 08:12:55):
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Db-derby Wiki for
change notification.
The
[
http://issues.apache.org/jira/browse/DERBY-528?page=comments#action_12416339 ]
Kathey Marsden commented on DERBY-528:
--
Thanks so much for this important fix.
Can you test this change with
- new server/10.1.1.0 client
-new client/10.1.1.0
David Van Couvering wrote:
http://wiki.apache.org/db-derby/ForwardCompatibility
[snip - stuff about 2 votes that sounds fine to me]
I'd also
like to make sure there aren't any lingering issues with the Wiki page
as it stands, before I go through the process of running a vote.
First
[ http://issues.apache.org/jira/browse/DERBY-920?page=all ]
Bryan Pendleton updated DERBY-920:
--
Attachment: updatedDiff.txt
The change looks clean. The copyright change to sysinfo's Main.java no longer
applies,
as Andrew rewrote that copyright message
[Auto-generated mail]
*TinderBox_Derby* 414563/2006-06-15 13:42:38 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1673672 2 142.93% SunOS-5.10_i86pc-i386
Details in
Add new, lengthless overloads to the streaming api
--
Key: DERBY-1417
URL: http://issues.apache.org/jira/browse/DERBY-1417
Project: Derby
Type: New Feature
Components: JDBC
Versions: 10.2.0.0
Reporter:
[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ]
Rick Hillegas updated DERBY-1417:
-
Description:
The JDBC4 Expert Group has approved a new set of overloads for the streaming
methods. These overloads do not take a length argument. Here are
[ http://issues.apache.org/jira/browse/DERBY-1417?page=all ]
Rick Hillegas updated DERBY-1417:
-
Attachment: derby-1417-01-castsInTests.diff
Attaching derby-1417-01-castsInTests.diff. This patch adds some casts to some
jdbc4 tests so that they will
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416356 ]
Rick Hillegas commented on DERBY-1399:
--
I'm afraid that even with this patch, I'm still seeing the following diff in
the DerbyNetAutoStart test when run under mustang
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416359 ]
Olav Sandstaa commented on DERBY-1399:
--
Comments to Kathey's concerns about this patch (or rather the change introduced
in DERBY-930):
Autoloading of JDBC drivers is a
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416361 ]
Olav Sandstaa commented on DERBY-1399:
--
Rick, The failure you see is not related to neither autoloading nor my patch.
This problem is reported separately in DERBY-803
On 6/15/06, Rick Hillegas (JIRA) derby-dev@db.apache.org wrote:
[
http://issues.apache.org/jira/browse/DERBY-1399?page=comments#action_12416356 ]
Rick Hillegas commented on DERBY-1399:
--
I'm afraid that even with this patch, I'm still seeing the
Note that this change is not as easy as it seems. I believe there
are all sorts of upgrade issues. I don't think it is possible to
change the name in 10.1 as 2 different versions of CS running in
different jvms won't agree on the object they are locking.
I guess for a hard upgrade one could
I know it is small, but probably best to create a jira and attach the
patch there, just so standard processes are used.
Mamta Satoor wrote:
Hi,
I noticed that Andrew had to recently make a checkin # 413411 because
JitTest.java prints out Derby version, name and driver name. In order to
What state is the 10.1 branch for checkins, I don't want to cause
trouble for the 10.1.3 release. I may want to backport the fix for
DERBY-1392, after it goes into trunk. Any reason to wait?
/mikem
On 6/12/06, Satheesh Bandaram [EMAIL PROTECTED]
wrote:
Rick Hillegas wrote: If memory use is not a problem for your environment, set this property to a high number; allowing the optimizer the maximum
flexibility in considering a join strategy queries involving large queries leads to better
derbyall/storeall/storemore/OnlineBackupTest3 failed, unable to reproduce
-
Key: DERBY-1418
URL: http://issues.apache.org/jira/browse/DERBY-1418
Project: Derby
Type: Bug
Components:
[ http://issues.apache.org/jira/browse/DERBY-1418?page=all ]
Mike Matrigali updated DERBY-1418:
--
Fix Version: 10.2.0.0
derbyall/storeall/storemore/OnlineBackupTest3 failed, unable to reproduce
There are 2 issues in the Tuning Guide that need to be corrected. Before the text can be updated there are several questions
that need to be answered. The questions are posted in the jira issue #1397. Can someone respond to these questions?
Thanks!-- Laura Stewart
derbyall/i18nTest/MessageBundleTest.diff test failed in nightly run, jdk15
--
Key: DERBY-1419
URL: http://issues.apache.org/jira/browse/DERBY-1419
Project: Derby
Type: Bug
Components:
On 6/15/06, Mike Matrigali [EMAIL PROTECTED] wrote:
What state is the 10.1 branch for checkins, I don't want to cause
trouble for the 10.1.3 release. I may want to backport the fix for
DERBY-1392, after it goes into trunk. Any reason to wait?
Let me bump the version, then feel free to check
I ran derbyall with this 10.2.0.2 snapshot onlinux - Linux Suse 9.2with IBM jdks - 1.4.2 and 1.5. I ran IBM jdk 1.5
with (-Xjit:count=0) and without jit option. Here are the details about the environment, test results,and failures:-
Summary
--
No new failure except the known failures
Mike Matrigali wrote:
What state is the 10.1 branch for checkins, I don't want to cause
trouble for the 10.1.3 release. I may want to backport the fix for
DERBY-1392, after it goes into trunk. Any reason to wait?
The 10.1 branch should be open for commits all the time, an impending
release
[ http://issues.apache.org/jira/browse/DERBY-1392?page=all ]
Mike Matrigali updated DERBY-1392:
--
Version: 10.2.0.0
I reviewed this patch, ran full derbyall, and committed it to the trunk with
following svn:
m1_142:129svn commit
Sending
[ http://issues.apache.org/jira/browse/DERBY-1408?page=all ]
Mike Matrigali reassigned DERBY-1408:
-
Assign To: Mike Matrigali
derbyall/jdbcapi/ScrollResultSetTest failed
---
Key: DERBY-1408
[ http://issues.apache.org/jira/browse/DERBY-1408?page=all ]
Mike Matrigali resolved DERBY-1408:
---
Fix Version: 10.2.0.0
Resolution: Fixed
As suggested disabling this test on j9 by setting the runwithj9=false property.
j9 is a jdk1.3 level
[Auto-generated mail]
*TinderBox_Derby* 414624/2006-06-15 17:52:36 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1673672 2 143.03% SunOS-5.10_i86pc-i386
Details in
Bryan Pendleton wrote:
The traces look good to me, although of course it is always hard to
read traces,
it's just a fact of life.
True, traces are hard to read. Thanks very much for going through them
Bryan.
You mentioned that this is a server-only patch at this point; have you
started
Hi,
We request everyone to please look at the JMX requirement for Derby
Document at the Derby wiki and *please* assign priorities to the
listed features or comment if they feel anything is missing.
We will be freezing the requirements document on 18th June so I
request you to please review the
Bernt M. Johnsen wrote:
Is it possible to get some synergy between this project and ddl-utils?
(See http://db.apache.org/derby/integrate/db_ddlutils.html)
Right... Jean and myself were just looking at ddlUtils yesterday and
forwarded relavent links to Ramin. This will be looked at during
[
http://issues.apache.org/jira/browse/DERBY-1419?page=comments#action_12416381 ]
Manjula Kutty commented on DERBY-1419:
--
This test failed with ibm142 and 15 jvms also
derbyall/i18nTest/MessageBundleTest.diff test failed in nightly run, jdk15
[
http://issues.apache.org/jira/browse/DERBY-1409?page=comments#action_12416382 ]
Michelle Caisse commented on DERBY-1409:
This is for new tests. I will use BaseJDBCTestCase. Thanks for the
information. Feel free to close this issue.
So I think -- The server max size for blocksize should be 10M because
that is the limit that is allowed by the spec. From my understanding of
the spec, the server does not get to choose the blocksize for QRYDTA. It
is the client which sends the qryblksz.
I agree with your analysis of the
[ http://issues.apache.org/jira/browse/DERBY-1360?page=all ]
Mike Matrigali updated DERBY-1360:
--
Component: SQL
Version: 10.2.0.0
Implement SQL Unicode character string literal
--
Key:
[ http://issues.apache.org/jira/browse/DERBY-1302?page=all ]
Mike Matrigali updated DERBY-1302:
--
Component: Network Client
Indent source files touched in DERBY-326
Key: DERBY-1302
URL:
[
http://issues.apache.org/jira/browse/DERBY-578?page=comments#action_12416403 ]
Rick Hillegas commented on DERBY-578:
-
Hi Manish,
I would like to take a look at this patch, but I get the following errors when
I try to apply it to my workspace. Could
[ http://issues.apache.org/jira/browse/DERBY-1413?page=all ]
Mike Matrigali reassigned DERBY-1413:
-
Assign To: Mike Matrigali
SQL State STORE_XA_XAER_DUPID does not have a matching message
Bryan Pendleton wrote:
So I think -- The server max size for blocksize should be 10M because
that is the limit that is allowed by the spec. From my understanding
of the spec, the server does not get to choose the blocksize for
QRYDTA. It is the client which sends the qryblksz.
I agree
[ http://issues.apache.org/jira/browse/DERBY-1420?page=all ]
Mamta A. Satoor updated DERBY-1420:
---
Attachment: JitTestpatch.txt
Make JitTest.java independent of Derby release
--
Key: DERBY-1420
Make JitTest.java independent of Derby release
---
Key: DERBY-1420
URL: http://issues.apache.org/jira/browse/DERBY-1420
Project: Derby
Type: Test
Components: Test
Reporter: Mamta A. Satoor
Assigned to: Mamta A.
[ http://issues.apache.org/jira/browse/DERBY-1409?page=all ]
Rick Hillegas closed DERBY-1409:
DerbyJUnitTest lacks String argument constructor
Key: DERBY-1409
URL:
Mike,
I just created DERBY-1420 for this issue and attached the patch to it.
thanks,
Mamta
On 6/15/06, Mike Matrigali [EMAIL PROTECTED] wrote:
I know it is small, but probably best to create a jira and attach thepatch there, just so standard processes are used.
Mamta Satoor wrote: Hi, I noticed
[ http://issues.apache.org/jira/browse/DERBY-1409?page=all ]
Rick Hillegas resolved DERBY-1409:
--
Resolution: Won't Fix
DerbyJUnitTest lacks String argument constructor
Key: DERBY-1409
[ http://issues.apache.org/jira/browse/DERBY-1413?page=all ]
Mike Matrigali updated DERBY-1413:
--
I was going to pick this one up, have you already fixed it - or is something
wierd going on?
I went to
68 matches
Mail list logo
