I am getting the exception below when running RunOptimizerTest (in
org.apache.derbyTesting.system.optimizer). My goal is to step through the query
compilation code to understand how it works. I am using Java 1.8. I am using
netbeans 8.0.1 and the class
path includes derbyrun.jar and
“connect 'jdbc:derby://10.4.26.101:1527/aps';”
However this fails with message:
ERROR 08001: java.net.ConnectException : Error connecting to server 10.4.26.100
on port 1,527 with message Connection refused
Assuming that your use of '.101' in the first line, and '.100' in
the third, was just
As a developer the normal "way" to find files to change together to
complete an issue is based on our own experience, debugging or through
the documentation, right?
Yes, I agree that is the normal way.
Also through code review, running tests, and messages from the compiler.
Is your idea that,
On 12/11/2015 3:56 AM, Anjana Prakash wrote:
Hi ,
Has anyone tried to retrieve table name based on their constraints.
Often you can do this sort of thing using JDBC's DatabaseMetaData:
http://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html
Alternately, have a look at the
My system procedure is accessing some of the derby utility function. At run
time of the procedure (in ij) it fails with exception
ERROR XJ001: Java exception: 'org/apache/derby/impl/load/Import:
java.lang.NoClassDefFoundError'.
In my stored procedure jar the manifest file has class-path
ERROR XIE0R: Import error on line 1 of file D:\derby\data\wincluster: The syntax
of the string representation of a date/time value is incorrect.
What's on line one of that file?
bryan
from line 1.
-Original Message-
From: Bryan Pendleton [mailto:bpendleton.de...@gmail.com]
ERROR XIE0R: Import error on line 1 of file D:\derby\data\wincluster:
The syntax of the string representation of a date/time value is incorrect.
What's on line one of that file?
Can you try
[
https://issues.apache.org/jira/browse/DERBY-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15042620#comment-15042620
]
Bryan Pendleton commented on DERBY-6845:
The new documentation looks very good to me.
I think you
On 12/3/2015 8:32 PM, Anjana Prakash wrote:
Hi,
Thanks for follow up. Following solved this issue
Glad to hear you figured it out!
Perhaps you could add your notes and the procedures
that worked for you to the Derby wiki?
http://wiki.apache.org/db-derby/FrontPage
bryan
On 12/2/2015 7:16 AM, Rick Hillegas wrote:
I would appreciate a review of the doc patch on
https://issues.apache.org/jira/browse/DERBY-6845
I'll have a look in the next day or so!
bryan
[
https://issues.apache.org/jira/browse/DERBY-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15039555#comment-15039555
]
Bryan Pendleton commented on DERBY-6845:
Hi Rick,
Thanks for putting together the draft
[
https://issues.apache.org/jira/browse/DERBY-6725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035169#comment-15035169
]
Bryan Pendleton commented on DERBY-6725:
Desk-checked the latest patch diff. Looks fine to me
Can I start derby code in debug mode from eclipse.
Yes, that should work fine, assuming that you have the right
overall configuration settings.
Derby is 100% pure Java, and any Java debugger can be used.
I often use JSwat, which is based on the Eclipse debugging
engine I believe.
I have also
On 12/1/2015 8:41 PM, Anjana Prakash wrote:
From my installed folder I start derby network server. Then from my java code
call import.importTable api of derby which I expected to come at the breakpoint
in my derby code
I think I understand, but maybe not, because I don't really
know what you
[
https://issues.apache.org/jira/browse/DERBY-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021410#comment-15021410
]
Bryan Pendleton commented on DERBY-6136:
FWIW, the "productize" patch built cleanly on
[
https://issues.apache.org/jira/browse/DERBY-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006017#comment-15006017
]
Bryan Pendleton commented on DERBY-6841:
I recall that System.currentTimeMillis can
What's the definition of "does not work successfully?
I'm not aware of such a limitation, but I imagine some classloading issues can
break
Thanks Kristian!
I realize the question was pretty vague.
Here's what little context there was:
In a separate forum, someone has claimed that multiple
connections to the same database from the same hosting
JVM does not work successfully if the database is an
in-memory database (uses jdbc:derby:memory:whatever).
Is this true?
If it is true, is it documented anywhere?
I didn't believe that
[
https://issues.apache.org/jira/browse/DERBY-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14966004#comment-14966004
]
Bryan Pendleton commented on DERBY-6839:
Is this possibly DERBY-6314?
> InvalidClassExcept
[
https://issues.apache.org/jira/browse/DERBY-6334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6334.
Resolution: Fixed
Fix Version/s: 10.13.0.0
Hi Kathey,
I agree, the test is running
[
https://issues.apache.org/jira/browse/DERBY-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14961584#comment-14961584
]
Bryan Pendleton commented on DERBY-5605:
Looks great! The new tests fail as I expected without
Here is a first draft of a release announcement for 10.12.1.1.
Looks great!
Thanks for all the hard work on the release, Rick.
bryan
On 9/20/2015 10:14 AM, Richard Hillegas wrote:
Please test-drive the 10.12.1.1 candidate, then vote on whether to accept it as
a Derby release.
+1
The release looks good to me.
bryan
[
https://issues.apache.org/jira/browse/DERBY-6811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877300#comment-14877300
]
Bryan Pendleton commented on DERBY-6811:
Thanks Rick.
I like the idea of teaching the tool
[
https://issues.apache.org/jira/browse/DERBY-6811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877179#comment-14877179
]
Bryan Pendleton commented on DERBY-6811:
Hi Rick,
Are you following http://wiki.apache.org/db
[
https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6834:
---
Summary: CURRENT_TIME and CURRENT_TIMESTAMP should support optional
precision argument
[
https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742636#comment-14742636
]
Bryan Pendleton commented on DERBY-6834:
I did some more studying of my 'firstTry.diff' patch
[
https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6834:
---
Attachment: firstTry.diff
I took a stab at this (see attached "firstTry.diff").
I
[
https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740851#comment-14740851
]
Bryan Pendleton commented on DERBY-6834:
Ah, I see, thank you. Accepting (and ignoring
java.sql.SQLTransacyionRollbackException:A lock could not be obtained within
the time requested
This might help; it has a lot of additional information about what
is happening with your application and how you can learn more about it:
http://wiki.apache.org/db-derby/LockDebugging
You
[
https://issues.apache.org/jira/browse/DERBY-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14740003#comment-14740003
]
Bryan Pendleton commented on DERBY-6834:
To be explicit, what would be different about your new
[
https://issues.apache.org/jira/browse/DERBY-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14736830#comment-14736830
]
Bryan Pendleton commented on DERBY-6733:
I'll log a related JIRA with the notion that we could
Bryan Pendleton created DERBY-6832:
--
Summary: Derby JMX Beans could be made self-describing for tools
like JConsole
Key: DERBY-6832
URL: https://issues.apache.org/jira/browse/DERBY-6832
Project
[
https://issues.apache.org/jira/browse/DERBY-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14736838#comment-14736838
]
Bryan Pendleton commented on DERBY-6733:
Possible follow-on project.
> Implement an MB
[
https://issues.apache.org/jira/browse/DERBY-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14736825#comment-14736825
]
Bryan Pendleton commented on DERBY-6825:
I updated to the head of trunk and tried some more
[
https://issues.apache.org/jira/browse/DERBY-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14733829#comment-14733829
]
Bryan Pendleton commented on DERBY-6831:
I looked at your log and didn't see anything particularly
[
https://issues.apache.org/jira/browse/DERBY-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734013#comment-14734013
]
Bryan Pendleton commented on DERBY-6829:
I agree; we want to avoid brittle documentation links
[
https://issues.apache.org/jira/browse/DERBY-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734016#comment-14734016
]
Bryan Pendleton commented on DERBY-6825:
I think your suggested CLOB conversion function would
[
https://issues.apache.org/jira/browse/DERBY-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734014#comment-14734014
]
Bryan Pendleton commented on DERBY-6829:
The updated page looks good to me. Thanks!
> Docum
On 9/5/2015 8:02 AM, Richard Hillegas wrote:
Please vote on the following proposed policy for supported platforms.
+1
thanks,
bryan
[
https://issues.apache.org/jira/browse/DERBY-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732056#comment-14732056
]
Bryan Pendleton commented on DERBY-6825:
Hi Rick, I was playing with this feature today to see how
[
https://issues.apache.org/jira/browse/DERBY-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732108#comment-14732108
]
Bryan Pendleton commented on DERBY-6733:
I was able to access all three of these beans using
[
https://issues.apache.org/jira/browse/DERBY-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732080#comment-14732080
]
Bryan Pendleton commented on DERBY-6829:
It would be nice if the documentation for the simpleJSON
[
https://issues.apache.org/jira/browse/DERBY-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14731641#comment-14731641
]
Bryan Pendleton commented on DERBY-6831:
Are you able to run your program in the embedded
ERROR XSDG0: Page Page(1325564,Container(0, 30832)) could not be read from disk.
Caused by: java.io.EOFException: Reached end of file while attempting to read a
whole page.
Does the derby.log have any more detail about this specific exception?
Note that you can use the system tables
On 9/3/2015 3:35 PM, Bergquist, Brett wrote:
Reached end of file while attempting to read a whole page
You should probably take a close read through all the
discussion on this slightly old Derby JIRA Issue:
https://issues.apache.org/jira/browse/DERBY-5234
There are some suggestions about how
I guess what I was expecting to see was the statement(s) were 50631 was
getting a lock on the MANAGED_HARDWARE_SUMMARY. I turned on statement logging
and see the issue. Your help here on how to read this output has help quite a
bit though. I did not understand that the output:
Granted
Lock : ROW, MANAGED_HARDWARE_SUMMARY, (47,8)
Waiting XID : {50633, S} , CSEM, SELECT CHASSIS_9145E10G_ID, IP_STR,
DS.TEMPLATE, DS.SYSTEM_TEMPLATE, DS.ADMIN_ENABLED, DS.ALIAS_NAME, DS.MODEL,
DS.HARDWARE_VERSION, DS.ACTIVE_FIRMWARE, DS.INACTIVE_FIRMWARE, DS.BOOTCODE,
CONTACT, CIRCUIT,
[
https://issues.apache.org/jira/browse/DERBY-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6807.
Resolution: Fixed
Fix Version/s: 10.12.0.0
We've completed all the planned work
[
https://issues.apache.org/jira/browse/DERBY-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14721551#comment-14721551
]
Bryan Pendleton commented on DERBY-6807:
Certainly. In fact, I thought I already
[
https://issues.apache.org/jira/browse/DERBY-6811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14721926#comment-14721926
]
Bryan Pendleton commented on DERBY-6811:
Viewed the release notes in my browser
[
https://issues.apache.org/jira/browse/DERBY-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713453#comment-14713453
]
Bryan Pendleton commented on DERBY-3535:
Possibly reproduced here:
http
[
https://issues.apache.org/jira/browse/DERBY-6786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6786:
---
Assignee: Abhinav Gupta
NullPointerException in INSERT INTO statement with multiple
[
https://issues.apache.org/jira/browse/DERBY-6779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14708152#comment-14708152
]
Bryan Pendleton commented on DERBY-6779:
Now that DERBY-6773 is complete
[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14707796#comment-14707796
]
Bryan Pendleton commented on DERBY-6773:
Abhinav, do you know of any additional
[
https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6803.
Resolution: Fixed
I think there is more consolidation and refactoring
that could be done
[
https://issues.apache.org/jira/browse/DERBY-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6823.
Resolution: Fixed
We have completed the work for this issue.
Refactor uses
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6802.
Resolution: Fixed
We have completed the work we planned for this issue.
Change
Hi Abhinav,
I think we have just one detail left for DERBY-6803, and
then I think we can mark it and DERBY-6773 completed.
Can you have a look at the Sqlca issue that I mentioned
in the comment on DERBY-6802 (and also referenced in
DERBY-6803)?
I think that maybe you can make a small patch
[
https://issues.apache.org/jira/browse/DERBY-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6804.
Resolution: Fixed
We have completed the work we intended for this issue.
Change
[
https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704958#comment-14704958
]
Bryan Pendleton commented on DERBY-6803:
Before we resolve this issue, we need
[
https://issues.apache.org/jira/browse/DERBY-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704945#comment-14704945
]
Bryan Pendleton commented on DERBY-6804:
We believe that SVN revision https
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14704959#comment-14704959
]
Bryan Pendleton commented on DERBY-6802:
The Sqlca issue mentioned above is more
[
https://issues.apache.org/jira/browse/DERBY-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6801.
Resolution: Fixed
Fix Version/s: 10.12.0.0
We have completed the intended work
[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6773:
---
Attachment: passesTests.diff
Hi Abhinav,
Your approach looks good to me.
Can you have
[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698427#comment-14698427
]
Bryan Pendleton commented on DERBY-6773:
Not every integrity constraint violation
[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698433#comment-14698433
]
Bryan Pendleton commented on DERBY-6773:
It seems that LANG_NULL_INTO_NON_NULL
[
https://issues.apache.org/jira/browse/DERBY-6830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14698038#comment-14698038
]
Bryan Pendleton commented on DERBY-6830:
The pages look great to me, thanks
[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6773:
---
Attachment: addToTestSuite.diff
Attached addToTestSuite.diff is my attempt to recast
[
https://issues.apache.org/jira/browse/DERBY-6773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6773:
---
Attachment: switchArgs.diff
I updated the engine's SQLExceptionFactory to throw
the new
[
https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6803:
---
Attachment: clientChanges.diff
Attached clientChanges.diff represents the current code we've
[
https://issues.apache.org/jira/browse/DERBY-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6823:
---
Assignee: Abhinav Gupta
Refactor uses of DB2_JCC_MAX_EXCEPTION_PARAM_LENGTH
Hi Abhinav,
Can you check over the latest commits I have done, and
make sure that we have committed the correct version of
the code changes for your patches on the DERBY-6773 subtasks?
I think we still have the following items to do for DERBY-6773:
1) Address the handling of
[
https://issues.apache.org/jira/browse/DERBY-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660038#comment-14660038
]
Bryan Pendleton commented on DERBY-6804:
I believe we have addressed this issue
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659319#comment-14659319
]
Bryan Pendleton commented on DERBY-6802:
Hi Abhinav,
I think this change has
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14659343#comment-14659343
]
Bryan Pendleton commented on DERBY-6802:
Actually, looking at it more closely
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6802:
---
Attachment: refactorServerCode.diff
Attached refactorServerCode is the server-side portion
[
https://issues.apache.org/jira/browse/DERBY-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14652822#comment-14652822
]
Bryan Pendleton commented on DERBY-6829:
Looks very good.
There's one instance
[
https://issues.apache.org/jira/browse/DERBY-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14651286#comment-14651286
]
Bryan Pendleton commented on DERBY-6829:
Docs look pretty good to me.
Near
Hi Abhinav,
Have you tried putting all the pieces together, and running the
original DERBY-6773 test case with all of your patches applied?
Or do you think we still have more pieces to put together first?
thanks,
bryan
On 7/25/2015 4:49 PM, Abhinav Gupta wrote:
Hi Bryan,
I studied your patch and it was helpful. But I still have doubts about the
implementation of getArgs() in MessageUtils
Hi Abhinav,
My idea for MessageUtils.getArgs() is that it will do the opposite
of
On 7/26/2015 10:15 AM, Abhinav Gupta (JIRA) wrote:
I've attached the patch MessageUtils_latest.diff again with the latest class.
Thanks Abhinav! The patch downloads and builds successfully for me.
It's starting to look very close, I think. Hopefully in my recent messages
I made my ideas
Another issue that I noticed was that getArgs() also needs to return the
messageId. One of the possible solutions that I could think of was to include
the messageId field as the last object of the Object array arguments and
retrieve it from there in
getLocalizedMessage(). Would it be a good
[
https://issues.apache.org/jira/browse/DERBY-6803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6803:
---
Attachment: clientOutline.diff
The attached clientOutline.diff does not compile
[
https://issues.apache.org/jira/browse/DERBY-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641831#comment-14641831
]
Bryan Pendleton commented on DERBY-6801:
Hi Abhinav,
You seem to be making very
[
https://issues.apache.org/jira/browse/DERBY-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638148#comment-14638148
]
Bryan Pendleton commented on DERBY-5466:
Your new classes would be packaged within
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14637633#comment-14637633
]
Bryan Pendleton commented on DERBY-6802:
That's an interesting observation. I
[
https://issues.apache.org/jira/browse/DERBY-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14637922#comment-14637922
]
Bryan Pendleton commented on DERBY-5466:
Contributions are wonderful, thanks
Yes, that is the right idea. I think the critical
code that we need to re-factor for the purpose of
splitting the sqlerrmc string back into the
arguments and messageID can be found at lines 154-186
of o.a.d.catalog.SystemProcedures.java in the java/engine directory.
Do we
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634331#comment-14634331
]
Bryan Pendleton commented on DERBY-6802:
This looks great; I'll run some tests
[
https://issues.apache.org/jira/browse/DERBY-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634448#comment-14634448
]
Bryan Pendleton commented on DERBY-6802:
My test runs with 6802.diff have shown
[
https://issues.apache.org/jira/browse/DERBY-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6821:
---
Attachment: moveTest.diff
It seems straightforward to move the XMLOptimizerTraceTest
class
[
https://issues.apache.org/jira/browse/DERBY-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6807:
---
Attachment: releaseNote.html
XXE attack possible by using XmlVTI and the XML datatype
[
https://issues.apache.org/jira/browse/DERBY-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6783.
Resolution: Fixed
Fix Version/s: 10.12.0.0
I believe we've completed all of our
[
https://issues.apache.org/jira/browse/DERBY-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6801:
---
Attachment: unsealDerbyNetJar.diff
My test failures involved running with jars, and it turns
[
https://issues.apache.org/jira/browse/DERBY-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6821.
Resolution: Fixed
Fix Version/s: 10.12.0.0
I've completed the work I intended
[
https://issues.apache.org/jira/browse/DERBY-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton updated DERBY-6807:
---
Issue fix info: Patch Available,Release Note Needed (was: Patch
Available)
XXE attack
[
https://issues.apache.org/jira/browse/DERBY-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632515#comment-14632515
]
Bryan Pendleton commented on DERBY-6807:
I think all that remains for this issue
[
https://issues.apache.org/jira/browse/DERBY-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6810.
Resolution: Fixed
We haven't thought of any additional tests to include, and the
existing
[
https://issues.apache.org/jira/browse/DERBY-6800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6800.
Resolution: Fixed
Fix Version/s: 10.12.0.0
I believe we've completed the work we
1001 - 1100 of 4628 matches
Mail list logo
