Knut Anders Hatlen created DERBY-5960:
-
Summary: VirtualRandomAccessFile.close() is not idempotent
Key: DERBY-5960
URL: https://issues.apache.org/jira/browse/DERBY-5960
Project: Derby
[
https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483054#comment-13483054
]
Knut Anders Hatlen commented on DERBY-5232:
---
The double closing of the readme
[
https://issues.apache.org/jira/browse/DERBY-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5960:
--
Attachment: d5960-1a.diff
Attaching a fix, including a test case in VirtualFileTest.
[
https://issues.apache.org/jira/browse/DERBY-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5960:
--
Issue fix info: Patch Available
VirtualRandomAccessFile.close() is not
On 10/17/12 10:18 AM, Rick Hillegas wrote:
When Kristian implemented database unencryption, I believe that he
just piggybacked on top of the existing re-encryption logic. This
means that unencryption records an EncryptContainerUndoOperation in
the transaction log just as re-encryption does.
[
https://issues.apache.org/jira/browse/DERBY-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483214#comment-13483214
]
Knut Anders Hatlen commented on DERBY-4480:
---
This does not appear to be a
entry format strikes me as a chunk of work that is not motivated by any
compelling evidence.
+1
As Ward Cunningham says, do the simplest thing that could possibly work [1]
thanks,
bryan
[1] http://www.artima.com/intv/simplest.html
[
https://issues.apache.org/jira/browse/DERBY-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483310#comment-13483310
]
Myrna van Lunteren commented on DERBY-4480:
---
This sounds like a jvm bug, then?
[
https://issues.apache.org/jira/browse/DERBY-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483329#comment-13483329
]
Kim Haase commented on DERBY-5928:
--
As a preliminary step, committed patch
[Auto-generated mail]
*Daily* 1401329/2012-10-23 18:00:08 MEST
Failed TestsOK Skip Duration Suite
---
*Jvm: 1.7*
lin
01755817558 0 .% suitesAll
01515 0 .% jdbcapiAutoLoad
014
[
https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-5232:
---
Attachment: DERBY5232_patch3_stat.txt
DERBY5232_patch3_diff.txt
Another
[
https://issues.apache.org/jira/browse/DERBY-4480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483349#comment-13483349
]
Knut Anders Hatlen commented on DERBY-4480:
---
I ran with jars, since auto-loading
[
https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen reassigned DERBY-4323:
-
Assignee: Knut Anders Hatlen
test failure in lang.ErrorMessageTest with IBM
[
https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483358#comment-13483358
]
Knut Anders Hatlen commented on DERBY-4323:
---
I saw this now with Java SE
I'm wondering what we should tell users about the new
SYSCS_INVALIDATE_STORED_STATEMENTS procedure. Should we say:
I) Run SYSCS_INVALIDATE_STORED_STATEMENTS whenever you think that your
metadata queries or triggers are mis-behaving.
II) Run SYSCS_INVALIDATE_STORED_STATEMENTS whenever you
On 10/24/2012 11:06 AM, Rick Hillegas wrote:
I'm wondering what we should tell users about the new
SYSCS_INVALIDATE_STORED_STATEMENTS procedure. Should we say:
I'd vote for 1 with a bit more of an explanation:
I) Run SYSCS_INVALIDATE_STORED_STATEMENTS whenever you think that your
metadata
[
https://issues.apache.org/jira/browse/DERBY-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5926:
-
Attachment: DERBY-5926.zip
DERBY-5926.stat
DERBY-5926.diff
Thanks for
[
https://issues.apache.org/jira/browse/DERBY-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-5926:
-
Issue fix info: Patch Available
Document user-defined aggregates (DERBY-672)
See https://builds.apache.org/job/Derby-docs/150/changes
Changes:
[chaase3] DERBY-5928 Add more task focus to Derby security documentation
Modified 4 Developer's Guide topics and added a new one.
Patch: DERBY-5928.diff
--
Started by an SCM change
[
https://issues.apache.org/jira/browse/DERBY-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483517#comment-13483517
]
Mamta A. Satoor commented on DERBY-5232:
To solve the UTF-8 vs UTF-16 problem
Thanks for both the question and the answer, Rick and Kathey. I'll
reopen DERBY-5793 to incorporate this information.
Currently the only guidance is This procedure can be especially useful
after an upgrade. Is that still true or should I replace it?
Thanks again,
Kim
On 10/24/12 02:29 PM,
[
https://issues.apache.org/jira/browse/DERBY-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase reopened DERBY-5793:
--
Reopening to add more content based on this information from Kathey Marsden:
Run
[
https://issues.apache.org/jira/browse/DERBY-5926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483564#comment-13483564
]
Rick Hillegas commented on DERBY-5926:
--
Thanks for the new documentation, Kim. It
Saw the error again on trunk last week. Will enter a jira for it.
On Mon, Oct 15, 2012 at 3:00 PM, Mamta Satoor msat...@gmail.com wrote:
Hi,
Has anyone seen following failure in test_09_MaxThreads_Invalid? This
happened 10.8 codeline revision 1395431, with ibm142 jdk on a Windows
machine.
[
https://issues.apache.org/jira/browse/DERBY-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4631:
--
Issue fix info: Release Note Needed,Repro attached (was: Repro
attached,Patch Available)
Hello Derby-dev,
Attached are the draft release notes for 10.8.3. They actually say
10.8.2.3 because until I merge the versions the tool cannot be generated
with 10.8.3 as the release version.
Please review. I do have one question on the tool and generation. The
output says one issue
26 matches
Mail list logo