[Auto-generated mail]
*Derby* 385339/2006-03-12 19:45:52 CET
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
4643639 0 103.13% CYGWIN_NT-5.1_i686-unknown
NA NA NANA
[
http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370138 ]
Kristian Waagan commented on DERBY-1095:
No Jiras have been opened. First patch for Statement.isClosed() is not even
committed yet (DERBY-953). Code for
I had a look at the testsuite execution times for the last week and see
that two testsuites have had significant increases:
storetests: with svn 383955 (2006-03-07) duration increased
3 to 11 times depending on platform.
[
http://issues.apache.org/jira/browse/DERBY-919?page=comments#action_12370144 ]
Andreas Korneliussen commented on DERBY-919:
The main idea with this issue was to clean up the exisiting tests which inherit
from DerbyJUnitTest, so that they can
Ole Solberg wrote:
I had a look at the testsuite execution times for the last week and see
that two testsuites have had significant increases:
storetests: with svn 383955 (2006-03-07) duration increased
3 to 11 times depending on platform.
[ http://issues.apache.org/jira/browse/DERBY-1067?page=all ]
Andreas Korneliussen updated DERBY-1067:
Attachment: derbyall_report.txt
Attaching report from derbyall.
One test fails due to DERBY-734. Reran the test two times, and it succeeded
[ http://issues.apache.org/jira/browse/DERBY-1101?page=all ]
Knut Anders Hatlen updated DERBY-1101:
--
Attachment: testderby1101.java
Attaching a small program that tests what
EmbedResultSet40.getHoldability() returns when the result set is
returned
[
http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12370159 ]
Øystein Grøvlen commented on DERBY-690:
---
More review comments. This time for the changes to the access layer:
11. ScanController
11.1 fetchWithoutQualify()
a) I
[
http://issues.apache.org/jira/browse/DERBY-1086?page=comments#action_12370180 ]
Thorsten Möller commented on DERBY-1086:
I tried what is recommended by this thread but it doesn't work well. In
particular, setting the property derby.system.home to
[
http://issues.apache.org/jira/browse/DERBY-919?page=comments#action_12370182 ]
Kristian Waagan commented on DERBY-919:
---
I agree that the naming of the class can be changed.
I am not so sure if I fully agree with the proposed change regarding
[
http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12370184 ]
Dyre Tjeldvoll commented on DERBY-970:
--
So is the consensus NOT to change any queries in metadata.properties, then? And
add new versions of those queries that need to
Kristian Waagan (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370077 ]
Kristian Waagan commented on DERBY-1095:
I see your point, but I still think Derby is buggy. The repro script executes a
[
http://issues.apache.org/jira/browse/DERBY-1086?page=comments#action_12370187 ]
John H. Embretsen commented on DERBY-1086:
--
Thorsten,
In that case, I would say you have found a bug. However, I was not able to
reproduce it. Below is a
[
http://issues.apache.org/jira/browse/DERBY-1101?page=comments#action_12370189 ]
Daniel John Debrunner commented on DERBY-1101:
--
Thanks for following up on this Knut, you said:
Since the ResultSet object was produced by a Statement
[ http://issues.apache.org/jira/browse/DERBY-1094?page=all ]
Dyre Tjeldvoll updated DERBY-1094:
--
Attachment: derby-1094.preliminary.diff
I'm attaching a preliminary patch for the GetProcedureColumn.java and
TypeId.java part of this issue. The patch
Ole Solberg wrote:
I had a look at the testsuite execution times for the last week and see
that two testsuites have had significant increases:
nist: with svn 383172 (2006-03-04) duration increased
4 to 7 times depending on platform.
[
http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370210 ]
Knut Anders Hatlen commented on DERBY-1095:
---
Dan Debrunner wrote:
I do think it needs to be fixed, I don't think the Connection having
a list of open statements
[
http://issues.apache.org/jira/browse/DERBY-1080?page=comments#action_12370212 ]
Sunitha Kambhampati commented on DERBY-1080:
If there are no issues, I'd appreciate if someone can commit this patch
(derby1080.2.diff.txt). Thanks.
Here is
Hi,
I noticed in passing that a few of the store tests - for example, OnlineBackupTest1 - use hardcoded '/' in paths.
While I've not checked this, I am worrying that this test might not pass under DOS (note, it would be find under cygwin, but not everyone may have some such shell simulator).
Or
[
http://issues.apache.org/jira/browse/DERBY-897?page=comments#action_12370222 ]
Gregory Gerard commented on DERBY-897:
--
Yeah, this seems to be needed for proper embedding.
An Eclipse plugin is needed that can act as the Derby System Home, enabling
[
http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12370219 ]
Kathey Marsden commented on DERBY-970:
--
Knut Asked:
By the way, how strict is that rule (That metadata queries be handled on the
server side and not the client)?
The
While going through some of the Derbylist mails on Grant/Revoke, I realized that various database objects in a sqlStandard modemay require switching authorizers from the invoker to different definers and vice versa. This piece of task sounds interesting to me and hence I have following proposal
[
http://issues.apache.org/jira/browse/DERBY-1080?page=comments#action_12370217 ]
Bryan Pendleton commented on DERBY-1080:
I intend to submit this patch today. If any reviewers are still looking at it,
please let me know.
Connection reset when
[
http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12370231 ]
Kathey Marsden commented on DERBY-970:
--
Note: My previous comment had an error. I said:
For example adding the 10.2 metadata.properties to the 10.2 client and having
Change the client driver to allow statements to be garbage-collected once they
are not referenced in an application
---
Key: DERBY-1103
URL:
Andrew McIntyre wrote:
On 2/28/06, Jean T. Anderson [EMAIL PROTECTED] wrote:
Info needs to be added to the derby/docs/trunk documenting where files
came from outside the ASF.
What's the history behind fo2html.xsl getting committed to the Derby
repo? I keep thinking I should know that, but I'm
[ http://issues.apache.org/jira/browse/DERBY-1103?page=all ]
Deepa Remesh closed DERBY-1103:
---
Change the client driver to allow statements to be garbage-collected once
they are not referenced in an application
I'm still reviewing this patch and should be done very soon. I needed
to look at it as it is something I need to look at / handle for the
changes I made for USRSSBPWD support (JIRA-528).
Thanks,
--francois
On 3/13/06, Bryan Pendleton (JIRA) derby-dev@db.apache.org wrote:
[
[ http://issues.apache.org/jira/browse/DERBY-949?page=all ]
Myrna van Lunteren updated DERBY-949:
-
Attachment: DERBY-949_2006_03_13.diff
new patch (DERBY-949_2006_03_13.diff) because previous oneresulted in a
conflict when syncing up to a newer
yea that test, the reclaim_longcol has a few cases with relative
large rows, and some waits for post commit so it is
expected that it would take longer.
I would be surprised if nist changed at all.
Ole Solberg wrote:
Ole Solberg wrote:
I had a look at the testsuite execution times for the
[ http://issues.apache.org/jira/browse/DERBY-1071?page=all ]
Sunitha Kambhampati reopened DERBY-1071:
Make UserAuthenticator javadoc mention clearly about what is passed in
userName in authenticateUser
[
http://issues.apache.org/jira/browse/DERBY-970?page=comments#action_12370240 ]
David Van Couvering commented on DERBY-970:
---
To Dyre's question: I don't know if there is a consensus, but at least *I*
support adding new queries instead of
[ http://issues.apache.org/jira/browse/DERBY-1059?page=all ]
Anurag Shekhar updated DERBY-1059:
--
Attachment: derby-1059_2.diff
Move all the implemented methods of PreparedStatement40 and
EmbedPreparedStatement40 to the base class PreparedStatement and
On 2/28/06, Jean T. Anderson [EMAIL PROTECTED] wrote:
Info needs to be added to the derby/docs/trunk documenting where files
came from outside the ASF.
What's the history behind fo2html.xsl getting committed to the Derby
repo? I keep thinking I should know that, but I'm drawing a blank.
[ http://issues.apache.org/jira/browse/DERBY-1059?page=all ]
Anurag Shekhar updated DERBY-1059:
--
Attachment: derby-1059_3.diff
Move all the implemented methods of PreparedStatement40 and
EmbedPreparedStatement40 to the base class PreparedStatement and
[
http://issues.apache.org/jira/browse/DERBY-1059?page=comments#action_12370243 ]
Anurag Shekhar commented on DERBY-1059:
---
pleaseignore derby-1059_2.diff attached today its the same as privious patch.
call to stored procedure with out params fails
Finalization of statements in client driver should handle sending of CLSQRY to
close result sets on network server
--
Key: DERBY-1104
URL:
derbyall failures due to change in exception type
-
Key: DERBY-1105
URL: http://issues.apache.org/jira/browse/DERBY-1105
Project: Derby
Type: Sub-task
Versions: 10.0.2.0
Environment: jdk 1.6
Reporter:
[ http://issues.apache.org/jira/browse/DERBY-1021?page=all ]
Deepa Remesh closed DERBY-1021:
---
Fix Version: 10.2.0.0
Resolution: Fixed
This issue has been partly resolved by check-ins for DERBY-1103. A new sub-task
(DERBY-1104) is opened for
[ http://issues.apache.org/jira/browse/DERBY-1071?page=all ]
Sunitha Kambhampati updated DERBY-1071:
---
Attachment: Derby1071.2.diff.txt
Fix javadoc comment for authenticateUser#userName.
userName - The user's name for the connection request. May
Prepared statements are not garbage collected on the server until the sections
are reused
-
Key: DERBY-1106
URL: http://issues.apache.org/jira/browse/DERBY-1106
Project: Derby
[ http://issues.apache.org/jira/browse/DERBY-210?page=all ]
Deepa Remesh updated DERBY-210:
---
Assign To: (was: Deepa Remesh)
I have opened a sub-task (DERBY-1103) for the work I have done for this issue
for 10.2. I am unassigning myself from
[ http://issues.apache.org/jira/browse/DERBY-1002?page=all ]
Deepa Remesh updated DERBY-1002:
Assign To: (was: Deepa Remesh)
There are two minor todo items for this issue. I am not working on them
currently, hence unassigning myself.
Check that
[ http://issues.apache.org/jira/browse/DERBY-809?page=all ]
Kristian Waagan resolved DERBY-809:
---
Fix Version: (was: 10.1.3.0)
Resolution: Fixed
Documentation has been fixed. I will close this issue in a few days, unless
someone signals
[ http://issues.apache.org/jira/browse/DERBY-1080?page=all ]
Bryan Pendleton updated DERBY-1080:
---
Attachment: derby-1080-testSecMec.tmp
Sunitha, I had a strange failure in testSecMec in the DerbyNet framework.
This is on Linux, using Sun JDK 1.4,
Hello,
Have I missed why we are not allowed to delete stuff from Jira anymore?
I saw Kathey was unable to delete a comment, and I am not able to delete
an attachment I would like to replace.
I tried deleting from a issue I both reported and was assigned to (I was
even logged in!), but the
On 3/13/06, Kristian Waagan [EMAIL PROTECTED] wrote:
Have I missed why we are not allowed to delete stuff from Jira anymore?
I saw Kathey was unable to delete a comment, and I am not able to delete
an attachment I would like to replace.
I tried deleting from a issue I both reported and was
[
http://issues.apache.org/jira/browse/DERBY-1080?page=comments#action_12370265 ]
Sunitha Kambhampati commented on DERBY-1080:
Thanks Bryan.
No. I havent come across this test failing on my machines but I didnt run with
jdk141 on linux. I had
For existing databases JDBC metadata queries do not get updated properly
between maintenance versions.
---
Key: DERBY-1107
URL: http://issues.apache.org/jira/browse/DERBY-1107
I was able to reproduce the truncated output a couple more times just
by running standalone commands of the form:
java -Dframework=DerbyNet
org.apache.derbyTesting.functionTests.harness.RunTest derbynet/testSecMec.java
So I don't think that the issue involves an interaction with another
I think we can give this a shot, although it may be the cause for
confusion. Given that we don't have recoverability, we might as well
have multi-versioning :)
In the meantime, maybe we can log some bugs/feature requests against
JIRA? (a) ability to grant delete of elements of an issue
On 3/13/06, David W. Van Couvering [EMAIL PROTECTED] wrote:
In the meantime, maybe we can log some bugs/feature requests against
JIRA? (a) ability to grant delete of elements of an issue without being
able to delete the issue and (b) delete merely marks its status as
deleted, it does not
[
http://issues.apache.org/jira/browse/DERBY-1080?page=comments#action_12370273 ]
Francois Orsini commented on DERBY-1080:
The changes look good to me and thanks for adding a connection reset test.
My only minor comment would be to document a bit
[
http://issues.apache.org/jira/browse/DERBY-60?page=comments#action_12370274 ]
Kathey Marsden commented on DERBY-60:
-
The SYSIBM schema is used internally by Network Client and Network Server for
JDBC Metadata methods.
It has no impact externally
I'd like to use SanityManager in the 'shared' package hierarchy.
Options are:
- Cut-and-paste, but this means having two SanityState.tmpl files, which
seems odd. However, it would be the safest.
- Put into the shared package and have both engine and client jar files
pick up the same class.
The test jdbcapi/setTransactionIsolation.java fails with ibm jvm1.5
---
Key: DERBY-1108
URL: http://issues.apache.org/jira/browse/DERBY-1108
Project: Derby
Type: Bug
Components: Regression Test
Hi Myrna,
Backup does not enforce any restrictions on which separator to use and
does not do any conversions. It just passes path specified directly to
to java.io.File constructors to create File object. I think most VM's
on Windows/MAC understands / as a name separator and internally
lang/predicatePushdown.sql fails with wsdd5.6
-
Key: DERBY-1109
URL: http://issues.apache.org/jira/browse/DERBY-1109
Project: Derby
Type: Test
Components: Regression Test Failure
Versions: 10.2.0.0
[ http://issues.apache.org/jira/browse/DERBY-1042?page=all ]
Suresh Thalamati resolved DERBY-1042:
-
Resolution: Fixed
store/OnlineBackupTest3.java intermittently hangs
-
Key:
lang/subquery.sql fails with wsdd5.6
Key: DERBY-1110
URL: http://issues.apache.org/jira/browse/DERBY-1110
Project: Derby
Type: Test
Components: Regression Test Failure
Versions: 10.2.0.0
Environment: IBM wsdd5.6
OK, sounds good. I can't see what the issue would be either, since
compatibility is only an issue for released jars.
I am *hoping* to get this solved soon, but I have higher priority itches
to scratch right now.
David
Andrew McIntyre wrote:
On 3/13/06, David W. Van Couvering [EMAIL
[
http://issues.apache.org/jira/browse/DERBY-1109?page=comments#action_12370278 ]
A B commented on DERBY-1109:
This issue is the same as DERBY-1110--they both have the same query in them,
and that query is failing with the same row-ordering diff.
This diff is
[ http://issues.apache.org/jira/browse/DERBY-1110?page=all ]
A B closed DERBY-1110:
--
Resolution: Duplicate
This is a duplicate of DERBY-1109. The same query appears in both
lang/subquery.sql and lang/predicatePushdown.sql, and that query is causing
this
[ http://issues.apache.org/jira/browse/DERBY-1022?page=all ]
Deepa Remesh reopened DERBY-1022:
-
Assign To: (was: Satheesh Bandaram)
I see this test fail with similar diff with IBM and Sun JDK1.3.1 in
derbynetclientmats suite. I think the
Mamta Satoor wrote:
While going through some of the Derbylist mails on Grant/Revoke, I
realized that various database objects in a sqlStandard modemay
require switching authorizers from the invoker to different definers
and vice versa. This piece of task sounds interesting to me and hence
Is there any hash joins in this plan? That is the standard reason to see
different ordering on different jvm/machine if plans look the same.
A B (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1109?page=comments#action_12370278 ]
A B commented on DERBY-1109:
Mamta Satoor wrote:
While going through some of the Derbylist mails on Grant/Revoke, I
realized that various database objects in a sqlStandard mode may require
switching authorizers from the invoker to different definers and vice
versa. This piece of task sounds interesting to me and hence I
[ http://issues.apache.org/jira/browse/DERBY-1080?page=all ]
Bryan Pendleton updated DERBY-1080:
---
Attachment: testSecMec_with_prints.tmp
testSecMec.DerbyNet.shutdown.std.log_with_prints
The bug reproduces with the print statements in
[ http://issues.apache.org/jira/browse/DERBY-1080?page=all ]
Sunitha Kambhampati updated DERBY-1080:
---
Attachment: DebugTest.diff.txt
derbyTesting.jar
I am attaching a DebugTest.diff.txt which adds some println statements to
getStatement() for a ResultSet returned from a procedure in embedded mode must
return the Statement that executed the CALL procedure
Key: DERBY-
David W. Van Couvering wrote:
OK, sounds good. I can't see what the issue would be either, since
compatibility is only an issue for released jars.
I think this is ok.
The only issue I see is that someone might see it as a precedent and
start importing hither and yon.
Ideally the insane build
Thanks, Dan and Satheesh, for your comments. I can see why having the authorizer information at LanguageConnectionContext won't work. I will look into putting this information in StatementContext, similar to what is done for SQL permissions for routines.
thanks,
Mamta
On 3/13/06, Daniel John
[
http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370305 ]
Daniel John Debrunner commented on DERBY-1095:
--
Knut wrote:
In the client driver, NetConnection maintains a WeakHashMap with all
open statements. When the
73 matches
Mail list logo
