[
http://issues.apache.org/jira/browse/DERBY-1603?page=comments#action_12426160 ]
Yip Ng commented on DERBY-1603:
---
Found the problem, will post the patch up for review after running some initial
tests.
> ERROR 54038: "Maximum depth of nested trig
[
http://issues.apache.org/jira/browse/DERBY-1621?page=comments#action_12426162 ]
Yip Ng commented on DERBY-1621:
---
Running some initial tests on this patch as well, will post it up for review
soon. While going through the SPSDescriptor implementa
[ http://issues.apache.org/jira/browse/DERBY-939?page=all ]
Yip Ng resolved DERBY-939.
--
Fix Version/s: 10.2.0.0
Resolution: Fixed
> NullPointerException at ResultSet.close() time for simple query using UNION
> and INTERSECT
> ---
[ http://issues.apache.org/jira/browse/DERBY-700?page=all ]
V.Narayanan reassigned DERBY-700:
-
Assignee: (was: V.Narayanan)
Hi,
I am not working actively on this issue. Hence unassigning myself from this
issue and moving on to other issues I am work
[Auto-generated mail]
*Derby* 429163/2006-08-06 19:46:01 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
NA NA NANA SunOS-5.10_i86pc-i386
Details in
http://www.multinet.no/~s
[
http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12426175 ]
John H. Embretsen commented on DERBY-1564:
--
This was only seen on the combination of Solaris OS and Sparc processors during
10.2.0.4 snapshot testing at S
Rajesh Kartha (JIRA) wrote:
I also think the title of the issue also need to change to reflect that self
trigger does not throw ERROR 54038 in some cases.
A few questions/concerns on this issue:
1) CORRECT TRIGGER DEFINITION:
To get the semantics the user seems to want, which is to upda
Update trigger updating the same rows as the original update does not throw an
exception ERROR 54038: "Maximum depth of nested triggers was exceeded" as it
should
-
[ http://issues.apache.org/jira/browse/DERBY-1603?page=all ]
Kathey Marsden resolved DERBY-1603.
---
Resolution: Invalid
This issue is being closed as invalid and a new issue DERBY-1652 filed with the
correct description. The actual problem is that the e
[
http://issues.apache.org/jira/browse/DERBY-1637?page=comments#action_12426221 ]
Tomohito Nakayama commented on DERBY-1637:
--
I confirmed to execute derbynet/OutBufferedStream.java with derby1637.draft.txt
and found it passes in my deve
[
http://issues.apache.org/jira/browse/DERBY-1029?page=comments#action_12426223 ]
Rick Hillegas commented on DERBY-1029:
--
Thanks for tripping across this, Kristian. I have deleted the directory of
empty files (lang) with subversion revision
[ http://issues.apache.org/jira/browse/DERBY-1639?page=all ]
Rick Hillegas updated DERBY-1639:
-
Derby Info: [Release Note Needed] (was: [Patch Available, Release Note
Needed])
Lowering the "patch available" flag until this issue settles.
> Include ear
[
http://issues.apache.org/jira/browse/DERBY-1564?page=comments#action_12426228 ]
John H. Embretsen commented on DERBY-1564:
--
I have spent much of the past few days trying to reproduce this failure and to
get to know more about whether
[
http://issues.apache.org/jira/browse/DERBY-1652?page=comments#action_12426232 ]
Daniel John Debrunner commented on DERBY-1652:
--
Does the comment "However, If the derby jars are updated to a new version" mean
that the bug is fixed
[ http://issues.apache.org/jira/browse/DERBY-694?page=all ]
V.Narayanan updated DERBY-694:
--
Attachment: DERBY-694_v4.diff
DERBY-694_v4.stat
I was earlier checking for the severity of the exception by,
netSqlca.getSqlCode() > ExceptionSeveri
[
http://issues.apache.org/jira/browse/DERBY-1637?page=comments#action_12426235 ]
Tomohito Nakayama commented on DERBY-1637:
--
I meant ibm131 on Linux...
> OutBufferedStream.java fails on ibm131/jdk131 jvms.
> ---
[
http://issues.apache.org/jira/browse/DERBY-1554?page=comments#action_12426239 ]
Rick Hillegas commented on DERBY-1554:
--
Thanks, Yip. The edits look good to me. As a sanity check, I'm running derbyall
on my linux machine. Will commit if th
[
http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12426238 ]
Daniel John Debrunner commented on DERBY-694:
-
Why is getting the severity from the SQLSate better than from the SQL code?
> Statement exceptions cause
[
http://issues.apache.org/jira/browse/DERBY-1652?page=comments#action_12426240 ]
Kathey Marsden commented on DERBY-1652:
---
Dan asked:
>Does the comment "However, If the derby jars are >updated to a new version"
>mean that the bug is fixed
Kathey Marsden wrote:
A few questions/concerns on this issue:
1) CORRECT TRIGGER DEFINITION:
To get the semantics the user seems to want, which is to update the
timestamp when TESTID changes, is this how the trigger should be defined?
[snip wrong syntax]
Answer is no. Not sure why I
The 10.2 wiki page (http://wiki.apache.org/db-derby/TenTwoRelease), in
its "Bug Fix Candidates" section now contains a link to all
open/reopened issues which are targetted for 10.2 and which have raised
their "patch available" flags.
Regards,
-Rick
Kathey Marsden wrote:
Kathey Marsden wrote:
A few questions/concerns on this issue:
1) CORRECT TRIGGER DEFINITION:
I think this is it. To update the timestamp when info is updated we do
this:
with 10.1.2.4
ij version 10.1
ij> connect 'jdbc:derby:wombat;create=true';
ij> CREATE TABLE
[
http://issues.apache.org/jira/browse/DERBY-1640?page=comments#action_12426254 ]
Rick Hillegas commented on DERBY-1640:
--
Committed at subversion revision 429365.
> Instability in XATest
> -
>
> Key: DERB
[ http://issues.apache.org/jira/browse/DERBY-1640?page=all ]
Rick Hillegas updated DERBY-1640:
-
Derby Info: (was: [Patch Available])
> Instability in XATest
> -
>
> Key: DERBY-1640
> URL: http://issue
Kathey Marsden wrote:
> Kathey Marsden wrote:
>
>> Kathey Marsden wrote:
>>
>>> A few questions/concerns on this issue:
>>> 1) CORRECT TRIGGER DEFINITION:
>>
>>
>>
> I think this is it. To update the timestamp when info is updated we do
> this:
> 0 rows inserted/updated/deleted
> ij> CRE
[
http://issues.apache.org/jira/browse/DERBY-694?page=comments#action_12426256 ]
V.Narayanan commented on DERBY-694:
---
Doing a getSqlCode() on NetSqlCa in the above case was returning a -1. This
value is less than ExceptionSeverity.STATEMENT_SE
Issue Subscription
Filter: Derby: JIRA issues with patch available (18 issues)
Subscriber: derby-dev
Key Summary
DERBY-1554 IDENTITY_VAL_LOCAL() returned value is modified incorrectly by a
multi-row INSERT statement.
http://issues.apache.org/jira/browse/DERBY-1554
DERBY-1533
[ http://issues.apache.org/jira/browse/DERBY-1643?page=all ]
Mamta A. Satoor updated DERBY-1643:
---
Derby Info: [Patch Available]
> As per the functional spec attached to DERBY-1330, a "revoke execute ...
> restrict" should fail if there are dependent o
[ http://issues.apache.org/jira/browse/DERBY-1597?page=all ]
Ramandeep Kaur updated DERBY-1597:
--
Attachment: DERBY-1597.diff
Submitting patch for DERBY-1597. Please review it.
> Scripts in frameworks direcotry needs to be revisted to set up CLASSPATH
I wouldn't mind the delay. Let us know what answer comes around on this
one.
Daniel John Debrunner (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1377?page=comments#action_12425969 ]
Daniel John Debrunner commented on DERBY-1377:
--
[ http://issues.apache.org/jira/browse/DERBY-1470?page=all ]
Ramandeep Kaur updated DERBY-1470:
--
Attachment: DERBY-1470.diff
Submitting diffs. Please review it.
> Correct instructions in demo html file demo\simple\example.html
> ---
Daniel John Debrunner wrote:
Then I think this would lead to a simpler action statement of
UPDATE TEST SET TIMESTAMP = CURRENT_TIMESTAMP WHERE TESTID = OLD.TESTID
A statement trigger might be best in this case, would result in a single
update statement rather than N.
Hmmm
Well, this (
Hi All,
I ran code coverage for trunk - svn revision no 428586 with sun jdk131, sun jdk142, sun jdk15, and sun jdk16 on Windows 2000, and results are as following:-
OVERALL COVERAGE SUMMARY
Classes: 93% (1177/1260)
Methods: 78% (16331/20921)
Blocks: 75% (490643/658117)
Lines: 75% (101611.2/13
[ http://issues.apache.org/jira/browse/DERBY-1548?page=all ]
Laura Stewart updated DERBY-1548:
-
Attachment: derby1548_ref2.diff
derby1548_ref_html2.zip
Updated the text based on the comments received.
Attached an updated zip file which co
[
http://issues.apache.org/jira/browse/DERBY-1549?page=comments#action_12426270 ]
Laura Stewart commented on DERBY-1549:
--
Please review and answer the question that I posted on 8/3.
> Document support for JDBC escape functions: ACOS, ASIN,
Kathey Marsden wrote:
> Daniel John Debrunner wrote:
>
>> Then I think this would lead to a simpler action statement of
>>
>> UPDATE TEST SET TIMESTAMP = CURRENT_TIMESTAMP WHERE TESTID = OLD.TESTID
>>
>> A statement trigger might be best in this case, would result in a single
>> update statement
Another way is to specify which column in the trigger that will invoke the trigger action. i.e.:CREATE TRIGGER update_test AFTER UPDATE OF INFO ON test REFERENCING OLD AS old FOR EACH ROW MODE DB2SQL
UPDATE test SET timestamp=current_timestamp WHERE testid=old.testid;On 8/7/06, Ka
[Auto-generated mail]
*TinderBox_Derby* 429352/2006-08-07 16:22:25 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1687686 2 143.36% SunOS-5.10_i86pc-i386
Details in
http://www.mult
[
http://issues.apache.org/jira/browse/DERBY-1637?page=comments#action_12426272 ]
Sunitha Kambhampati commented on DERBY-1637:
Thanks Tomohito for trying it out. If it looks ok, it would be great if you
could commit this change.
[ http://issues.apache.org/jira/browse/DERBY-1633?page=all ]
A B updated DERBY-1633:
---
Attachment: DERBY-1633_v1.html
d1633_v1_reviewOnly.patch
Attaching a detailed description of the issue that is causing this regression,
and a description of what
I've spent a lot of time trying to understand the problem reported in DERBY-1633
and have just attached a description of the issue, along with a proposed fix, to
that Jira entry.
The fix isn't ready for commit, though, because it includes some changes for
predicate remapping that I don't fully
Thanks, Ramandeep. Our code coverage seems to have improved modestly.
For comparison, I'm attaching the results of your code-coverage run
against 10.1.3.
Regards,
-Rick
10.2 run:
Ramandeep Kaur wrote:
Hi All,
I ran code coverage for trunk - svn revision no 428586 with sun
jdk131, sun jdk1
Yip Ng wrote:
Another way is to specify which column in the trigger that will invoke
the trigger action.
Thanks Yip and Dan.I will hold off on the release note until we
have the fix and I understand the root cause and when the proper
checking is/is not done. For example I'd like to
Rick Hillegas wrote:
> Thanks, Ramandeep. Our code coverage seems to have improved modestly.
> For comparison, I'm attaching the results of your code-coverage run
> against 10.1.3.
There is a history of code coverage here:
http://wiki.apache.org/db-derby/CodeCoverage
Dan.
On 8/7/06, Ramandeep Kaur <[EMAIL PROTECTED]> wrote:
Hi All,
I ran code coverage for trunk - svn revision no 428586 with sun jdk131, sun
jdk142, sun jdk15, and sun jdk16 on Windows 2000, and results are as
following:-
These results now viewable at:
http://people.apache.org/~fuzzylogic/codec
[
http://issues.apache.org/jira/browse/DERBY-1554?page=comments#action_12426282 ]
Rick Hillegas commented on DERBY-1554:
--
Committed derby1554trunkdiff02.txt at subversion revision 429425. As Yip says,
derbyall only shows the expected diffs
[ http://issues.apache.org/jira/browse/DERBY-1554?page=all ]
Rick Hillegas updated DERBY-1554:
-
Derby Info: [Existing Application Impact, Regression] (was: [Existing
Application Impact, Patch Available, Regression])
> IDENTITY_VAL_LOCAL() returned valu
[ http://issues.apache.org/jira/browse/DERBY-1554?page=all ]
Kathey Marsden updated DERBY-1554:
--
Derby Info: [Regression] (was: [Existing Application Impact, Regression])
Now that this is fixed and we have returned to the previous behavior, there
shou
The JUnit setup now has methods that allow a test to check to see if the
vm supports levels of JDBC. The methods are in the class JDBC.
JDBC.vmSupportsJDBC2() // JDBC 2.0 or greater
JDBC.vmSupportsJDBC3() // JDBC 3.0 or greater
JDBC.vmSupportsJDBC4() // JDBC 4.0 or greater
JDBC.vmSupportsJSR169()
[ http://issues.apache.org/jira/browse/DERBY-528?page=all ]
Francois Orsini updated DERBY-528:
--
Attachment: 528_stat_v4.txt
528_diff_v4.txt
Sunitha, many thanks for this excellent and thorough review.
I've addressed all of the comments
[
http://issues.apache.org/jira/browse/DERBY-1377?page=comments#action_12426294 ]
Daniel John Debrunner commented on DERBY-1377:
--
The question on legal-discuss
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200608.mbox/[
[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ]
Deepa Remesh updated DERBY-1130:
Attachment: d1130-client-v1.diff
d1130-client-v1.status
Attaching a patch 'd1130-client-v1.diff' which disallows databaseName attribute
to be s
[ http://issues.apache.org/jira/browse/DERBY-1130?page=all ]
Deepa Remesh updated DERBY-1130:
Fix Version/s: 10.2.0.0
Derby Info: [Patch Available]
> Client should not allow databaseName to be set with setConnectionAttributes
> ---
[
http://issues.apache.org/jira/browse/DERBY-1626?page=comments#action_12426319 ]
Rajesh Kartha commented on DERBY-1626:
--
I ran this test using Derby 10.2.0.5 alpha - (428936) jars on jdk15, ibm15
and jdk16 on Windows and Linux. No fail
[
http://issues.apache.org/jira/browse/DERBY-1646?page=comments#action_12426331 ]
Laura Stewart commented on DERBY-1646:
--
Thank you for your comments.
Before I start using "connection access" I want to make certain that we are not
making
Hi Bryan,
Thanks so much for reviewing the changes and for verifying the patches. I
appreciate your time with this.
3) Who will run these tests, and when? If all the execution code is
optional, how do we ensure that it doesn't get broken?
I still have a couple of more patches to post to co
[ http://issues.apache.org/jira/browse/DERBY-402?page=all ]
Rick Hillegas updated DERBY-402:
Derby Info: (was: [Patch Available])
> INTERSECT/EXCEPT/UNION operators don't agree with documented behavior.
> ---
[ http://issues.apache.org/jira/browse/DERBY-402?page=all ]
Rick Hillegas updated DERBY-402:
Attachment: derby-402_v02.diff
Attaching derby-402_v02.diff, which I committed at subversion revision 429484.
This removes some odd characters which prevented t
Dear Development Community,
I find myself very concerned about the small amount of feedback we have
gotten so far from the user community on 10.2. We have heard no feedback
really positive or negative on the major new features, like
grant/revoke, SUR, online-backup and JDBC 4.0. We've gotte
[
http://issues.apache.org/jira/browse/DERBY-1401?page=comments#action_12426348 ]
Manjula Kutty commented on DERBY-1401:
--
The patch for this issue had been comitted a while ago. Can we close it?
> TestDataReader class in jdbcapi/Stream.java
[ http://issues.apache.org/jira/browse/DERBY-1320?page=all ]
Manjula Kutty updated DERBY-1320:
-
Attachment: svn_diff_1320.txt
Sorry for my mistake. Please find the new attached patch. I have included the
bug number to the patch name. Please let me know
[ http://issues.apache.org/jira/browse/DERBY-1320?page=all ]
Manjula Kutty updated DERBY-1320:
-
Attachment: svn_stat_1320.txt
> Test lang/procedure.java fails with ibm1.5 jvm
> --
>
> Key: DERBY
Otherwise, if any of my answers above would make you uncomfortable with
committing the patches (or with approving their commit), please let me
know and I will try to address your concerns.
Hi Army,
I am comfortable with your responses, and in my opinion the 5 patches
are ready for commit.
Is
[
http://issues.apache.org/jira/browse/DERBY-1646?page=comments#action_12426357 ]
Laura Stewart commented on DERBY-1646:
--
I reread the sections on user authorization and user authentication... and I
now see that I was confused.
I will add t
Bryan Pendleton wrote:
>> Otherwise, if any of my answers above would make you uncomfortable
>> with committing the patches (or with approving their commit), please
>> let me know and I will try to address your concerns.
>
>
> Hi Army,
>
> I am comfortable with your responses, and in my opinion
[Auto-generated mail]
*TinderBox_Derby* 429468/2006-08-07 22:43:07 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1687686 2 147.55% SunOS-5.10_i86pc-i386
Details in
http://www.mult
[ http://issues.apache.org/jira/browse/DERBY-646?page=all ]
David Van Couvering updated DERBY-646:
--
Derby Info: [Patch Available, Release Note Needed]
> In-memory backend storage support
> -
>
> Key: D
[
http://issues.apache.org/jira/browse/DERBY-646?page=comments#action_12426368 ]
David Van Couvering commented on DERBY-646:
---
Are separate tests needed for this feature. Isn't this a configuration option,
e.g. couldn't we run the stor
[
http://issues.apache.org/jira/browse/DERBY-646?page=comments#action_12426372 ]
Daniel John Debrunner commented on DERBY-646:
-
Probably no new tests are required but some changes to ensure the feature is
tested, such as the ability
Hi, all. I've uploaded the scripts to
http://wiki.apache.org/db-derby/FixingLicenseHeader. This means you,
yes you, can help with the relicensing project. Take a look at the Wiki
page, all you need to know should be there.
It's *possible* that we don't have to get all this done in time for
David Van Couvering wrote:
> Hi, all. I've uploaded the scripts to
> http://wiki.apache.org/db-derby/FixingLicenseHeader. This means you,
> yes you, can help with the relicensing project.
Just to be pedantic, we are not relicensing Derby.
Dan.
I see your point about new classes added to the public API needing
javadoc, that seems reasonable.
By release, do you mean a Derby release or an ICLA? Assuming the
latter, I thought the ICLA issue had been cleared up. The ICLA has been
on file for some time, search for Stephen Fitch in
http
David Van Couvering wrote:
> I see your point about new classes added to the public API needing
> javadoc, that seems reasonable.
>
> By release, do you mean a Derby release.
I missed an 'e'. You checked the 'Release Note Needed' flag, why would a
release note be needed?
Dan.
I guess it's not a regression or bug, so not a release note, but I
didn't know how else to indicate that documentation was needed, given
that it's a new feature...
David
Daniel John Debrunner wrote:
David Van Couvering wrote:
I see your point about new classes added to the public API needin
David Van Couvering wrote:
> I guess it's not a regression or bug, so not a release note, but I
> didn't know how else to indicate that documentation was needed, given
> that it's a new feature...
A new Jira entry indicating documentation is needed. :-)
Dan.
[Auto-generated mail]
*TinderBox_Derby* 429515/2006-08-08 01:52:58 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1687686 2 147.62% SunOS-5.10_i86pc-i386
Details in
http://www.mult
[
http://issues.apache.org/jira/browse/DERBY-1565?page=comments#action_12426396 ]
Andrew McIntyre commented on DERBY-1565:
Committed revision 429543, which updates the headers in the source files. The
work to insert the header into the c
[
http://issues.apache.org/jira/browse/DERBY-1516?page=comments#action_12426397 ]
Craig Russell commented on DERBY-1516:
--
I have run derby-all with these changes, and no errors were reported.
Any other comments before I check this in?
> In
[ http://issues.apache.org/jira/browse/DERBY-1614?page=all ]
Andrew McIntyre resolved DERBY-1614.
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed to trunk with revision 429550.
> Test harness overrides heap size settings when
[ http://issues.apache.org/jira/browse/DERBY-1431?page=all ]
Andrew McIntyre resolved DERBY-1431.
Fix Version/s: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed -alt2 patch to trunk with revision 429551.
> T
[ http://issues.apache.org/jira/browse/DERBY-1320?page=all ]
Andrew McIntyre resolved DERBY-1320.
Resolution: Fixed
Derby Info: (was: [Patch Available])
Checked in patch svn_diff_1320.txt with revision 429561.
> Test lang/procedure.java fails
The issue below brings up an interesting question. The attached diff
for this issue adds derby.jar to the classpath so that the user can
run sysinfo and verify that their classpath is correct. However, a
minimally configured client would only have derbyclient.jar, and I
think we should be promotin
[ http://issues.apache.org/jira/browse/DERBY-1470?page=all ]
Andrew McIntyre updated DERBY-1470:
---
Attachment: derby-1470-alt.diff
Attaching alternate patch for this issue, which adds sysinfo to
derbyclient.jar, so that sysinfo can be obtained from a c
[ http://issues.apache.org/jira/browse/DERBY-1470?page=all ]
Andrew McIntyre updated DERBY-1470:
---
Derby Info: [Patch Available]
> Correct instructions in demo html file demo\simple\example.html
>
[
http://issues.apache.org/jira/browse/DERBY-1470?page=comments#action_12426436 ]
Daniel John Debrunner commented on DERBY-1470:
--
I would say step 4) above is wrong, the up front introduction examples should
not be giving the impres
[
http://issues.apache.org/jira/browse/DERBY-1597?page=comments#action_12426438 ]
Andrew McIntyre commented on DERBY-1597:
The attached patch is ok, but I think that we should put $CLASSPATH first in
the list of arguments to -cp, in case
[ http://issues.apache.org/jira/browse/DERBY-1470?page=all ]
Andrew McIntyre updated DERBY-1470:
---
Attachment: derby-1470-alt2.diff
Attaching a second version of the alternate solution for this issue, this
version also unseals the newly added impl/tool
On 8/3/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
I'll write up a note for BUILDING.txt, but I'd like to put in some more
material than "These error messages are to be expected." Something like a
real explanation of why the .java files appear to be out of sync with the
source .jj files.
Doe
[
http://issues.apache.org/jira/browse/DERBY-1432?page=comments#action_12426451 ]
Andrew McIntyre commented on DERBY-1432:
Hi Ole, check the derby.logs for these failures on your machines. They will
contain a "Warning: UnknkownHostExcept
[Auto-generated mail]
*TinderBox_Derby* 429551/2006-08-08 05:22:24 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1687686 2 144.37% SunOS-5.10_i86pc-i386
Details in
http://www.mult
Hi Army: I have reviewed your Derby-688 XML patches. Thanks for continuing improving XML support for Derby. I have applied the patches and was able to compile without any problems (except for the part where I have to modified the patches manually to remove the absolute paths). I think Bryan
91 matches
Mail list logo
