[ http://issues.apache.org/jira/browse/DERBY-1847?page=all ]
Yip Ng updated DERBY-1847:
--
Affects Version/s: 10.2.2.0
10.3.0.0
Description:
Following script causes the select statement below to assert in sane build.
ij connect
Andrew McIntyre wrote:
On 9/13/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Why are you giving up?
I still believe there is a possible solution to this, so that the Derby
community can ship with JDBC4 capability - to that end, I'm doing what I
can to try to find a solution with Sun on
[
http://issues.apache.org/jira/browse/DERBY-801?page=comments#action_12434613 ]
Suresh Thalamati commented on DERBY-801:
Thanks for working on this issue, Anders. I really like your solution to solve
this issue. Patch is very good, I
[Auto-generated mail]
*Derby* 443042/2006-09-13 19:46:12 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
1687686 0 106.90% SunOS-5.10_i86pc-i386
Details in
Suresh Thalamati (JIRA) derby-dev@db.apache.org writes:
4) I noticed, there is new encryption buffer created on every
writePage() call, if the database is encrypted. This may cause jvm
peak memory usage increase, when there is a checkpoint, if there are
lot of dirty pages in the cache and if
Jean T. Anderson wrote:
Myrna van Lunteren wrote:
On 9/13/06, Jean T. Anderson [EMAIL PROTECTED] wrote:
...
I'll try this on for size and upload a new review draft:
This release includes JDBC 4.0 functionality based on a pre-release of
Java SE 6. When you use Derby with a Java SE
Create full SQL export of Database (including INSERTs)
--
Key: DERBY-1851
URL: http://issues.apache.org/jira/browse/DERBY-1851
Project: Derby
Issue Type: Improvement
Components:
[
http://issues.apache.org/jira/browse/DERBY-790?page=comments#action_12434688 ]
Knut Anders Hatlen commented on DERBY-790:
--
Hi Francois,
Did your re-verification show any problems? Do you think the fix will make it
into 10.2?
[
http://issues.apache.org/jira/browse/DERBY-1589?page=comments#action_12434689 ]
Mamta A. Satoor commented on DERBY-1589:
Bryan, you definitely look like on the right track with the dependency manager.
I was just wondering though if
[ http://issues.apache.org/jira/browse/DERBY-1326?page=all ]
Knut Anders Hatlen updated DERBY-1326:
--
Attachment: derby-1326-cleanup_exceptions.diff
Attaching a patch (derby-1326-cleanup_exceptions.diff) with two small
cleanups in preparation for
[
http://issues.apache.org/jira/browse/DERBY-1659?page=comments#action_12434702 ]
Andreas Korneliussen commented on DERBY-1659:
-
I have just a minor comment on the doc: I have been testing this feature, and
found that descrbie also
[
http://issues.apache.org/jira/browse/DERBY-790?page=comments#action_12434700 ]
Francois Orsini commented on DERBY-790:
---
Did your re-verification show any problems?
I had expanded the current SqlExceptionTest.java but realized the
Rick Hillegas wrote:
Jean T. Anderson wrote:
Myrna van Lunteren wrote:
...
Nice team-writing, I have 1 more suggestion, how about mentioning
10.2.1 instead of 10.2?
Small nit: I believe that there's a dita variable for the release
identifier. I recommend using that variable. That way,
[
http://issues.apache.org/jira/browse/DERBY-1271?page=comments#action_12434712 ]
Daniel John Debrunner commented on DERBY-1271:
--
In the last sentence is final in the correct place? The follow-on release
will not have *Derby's*
[ http://issues.apache.org/jira/browse/DERBY-1833?page=all ]
Dag H. Wanvik updated DERBY-1833:
-
Fix Version/s: 10.2.1.0
Marking this to be fixed in 10.2.1 as well, keeping it open till
this has happened.
Remove messages made unused by implementation
Issue Subscription
Filter: Derby: JIRA issues with patch available (18 issues)
Subscriber: derby-dev
Key Summary
DERBY-1659 Document describe and show tables functionality
http://issues.apache.org/jira/browse/DERBY-1659
DERBY-801 Allow parallel access to data files.
Geir Magnusson Jr wrote:
Andrew McIntyre wrote:
On 9/13/06, Geir Magnusson Jr [EMAIL PROTECTED] wrote:
Why are you giving up?
I still believe there is a possible solution to this, so that the Derby
community can ship with JDBC4 capability - to that end, I'm doing what I
can to try to find
[
http://issues.apache.org/jira/browse/DERBY-1589?page=comments#action_12434716 ]
Mamta A. Satoor commented on DERBY-1589:
Bryan, I tried the following ij session (which is similar to the problem script
except that there are no grant
[
http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434718 ]
Knut Anders Hatlen commented on DERBY-1326:
---
Bryan, I'm not sure I understand what impact this could have on
DERBY-51. DERBY-51 is about server shutdown,
Rick Hillegas wrote:
I do not believe we have reached consensus on the readiness of 10.2.
There seem to be two broad groupings of opinion:
1) Some people believe that 10.2 is ready for release. These people
argue that we should downgrade the urgency of the remaining issues which
block us
Sounds very good!
David
Jean T. Anderson wrote:
[snip]
I'll try this on for size and upload a new review draft:
This release includes JDBC 4.0 functionality based on a pre-release of
Java SE 6. When you use Derby with a Java SE 6 virtual machine, Derby
will use its JDBC 3.0 drivers, just as
[
http://issues.apache.org/jira/browse/DERBY-1847?page=comments#action_12434721 ]
Mamta A. Satoor commented on DERBY-1847:
It looks like at alter table add column/drop column time, we need to go update
the column COLUMNS in SYSCOLPERMS
[
http://issues.apache.org/jira/browse/DERBY-1589?page=comments#action_12434722 ]
Bryan Pendleton commented on DERBY-1589:
Thanks Mamta! That is very helpful. My feeling is that the basic dependency
manager issue is generic, but the NPE
In compiling release notes, I came across a couple 10.2 JIRAs which I
would classify as features. I have added these to the end of the Beta
Summary table on the snapshot wiki page:
http://wiki.apache.org/db-derby/TenTwoSnapshot. They are: DERBY-1216,
DERBY-1019, DERBY-962, and DERBY-571.
[ http://issues.apache.org/jira/browse/DERBY-1806?page=all ]
Rick Hillegas updated DERBY-1806:
-
Urgency: Normal (was: Urgent)
Downgrading the urgency of this issue because no reproducible test-case has
surfaced.
Connection errors in 10.2.1.1 - not
[ http://issues.apache.org/jira/browse/DERBY-1782?page=all ]
Rick Hillegas updated DERBY-1782:
-
Downgrading the urgency of this issue. Although it violates the ANSI rules, I
don't think this issue should block the release at this point.
When a privilege
[ http://issues.apache.org/jira/browse/DERBY-1782?page=all ]
Rick Hillegas updated DERBY-1782:
-
Downgrading the urgency of this issue. Although we are violating the ANSI
rules, I don't think that this issue should block the release of 10.2.
When a
[ http://issues.apache.org/jira/browse/DERBY-1782?page=all ]
Rick Hillegas updated DERBY-1782:
-
Urgency: Normal (was: Urgent)
When a privilege is revoked at table level, Derby should only drop objects
that require that particular privilege and not
Jean T. Anderson (JIRA) wrote:
Here's the current notice:
Derby 10.2.1 includes JDBC 4.0 functionality based on a pre-release of Java
SE 6.
Do we want to be more precise than that? I had been thinking that Derby
was based upon the Proposed Final Draft, but now I think more likely
it's based
[ http://issues.apache.org/jira/browse/DERBY-1618?page=all ]
Myrna van Lunteren updated DERBY-1618:
--
Derby Info: [Regression] (was: [Patch Available, Regression])
store/BootAllTest.junit fails on with jdk13 based jvms
[ http://issues.apache.org/jira/browse/DERBY-1618?page=all ]
Myrna van Lunteren resolved DERBY-1618.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
fixed in 10.3 - leaving open until this has gotten merged into 10.2.1.
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
In compiling release notes, I came across a couple 10.2 JIRAs which I
would classify as features. I have added these to the end of the Beta
Summary table on the snapshot wiki page:
http://wiki.apache.org/db-derby/TenTwoSnapshot. They are:
Daniel John Debrunner wrote:
Jean T. Anderson (JIRA) wrote:
Here's the current notice:
Derby 10.2.1 includes JDBC 4.0 functionality based on a pre-release of Java
SE 6.
Do we want to be more precise than that? I had been thinking that Derby
was based upon the Proposed Final Draft, but now
I would like to build a release candidate soon. I would like to do this
even though we know that the 10.2 optimizer changes are risky. It has
been pointed out that that risk plagues all optimizer modifications and
that we must balance that risk against the substantial performance boost
Hi Myrna,
Can you point me at the JIRAs for the script restructuring?
Thanks,
-Rick
Myrna van Lunteren wrote:
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
In compiling release notes, I came across a couple 10.2 JIRAs which I
would classify as features. I have added these to the end
Rick Hillegas wrote:
I would like to build a release candidate soon. I would like to do this
even though we know that the 10.2 optimizer changes are risky. It has
been pointed out that that risk plagues all optimizer modifications and
that we must balance that risk against the substantial
Rick Hillegas wrote:
...
I would like to build a 10.2 release candidate once we remove the
following obstacles:
...
3) We need to clip the JDBC4 disclaimer to the 10.2 user guides.
I'll post a patch to DERBY-1271 by the end of tomorrow that rolls in the
rest of the feedback for wording and
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Can you point me at the JIRAs for the script restructuring?
It was DERBY-1032:
http://issues.apache.org/jira/browse/DERBY-1032
Doc was handled mainly with DERBY-1223:
http://issues.apache.org/jira/browse/DERBY-1223
andrew
[
http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434752 ]
Knut Anders Hatlen commented on DERBY-1326:
---
Deepa wrote:
* I think it is okay to re-use free/idle threads without closing
them. It may not be okay
Daniel John Debrunner wrote:
Rick Hillegas wrote:
I would like to build a release candidate soon. I would like to do this
even though we know that the 10.2 optimizer changes are risky. It has
been pointed out that that risk plagues all optimizer modifications and
that we must balance that
Thanks, Andrew. I have added this to the feature list.
Cheers,
-Rick
Andrew McIntyre wrote:
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Can you point me at the JIRAs for the script restructuring?
It was DERBY-1032:
http://issues.apache.org/jira/browse/DERBY-1032
Doc was handled
Meant to send this to the list...
David
---BeginMessage---
I believe it is OK for us to change the docs. Cloudscape does this all
the time and it's not considered a fork. We did this for Derby 10.1.
David
Lars Heill wrote:
There is still the issue of the JDBC3/4 disclaimer in the docs,
Rick Hillegas wrote:
I would like to build a 10.2 release candidate once we remove the
following obstacles:
[snip obstacles]
I'd like to try to get DERBY-1547 in, it is really important to know
what version folks have.
Narayan posted a new patch. I will try to get it into the trunk today.
[ http://issues.apache.org/jira/browse/DERBY-1706?page=all ]
Mamta A. Satoor reassigned DERBY-1706:
--
Assignee: Mamta A. Satoor
NullPointerException occurs when trying to create a table in schema SESSION
[ http://issues.apache.org/jira/browse/DERBY-1706?page=all ]
Mamta A. Satoor updated DERBY-1706:
---
Attachment: DERBY1706NPEwithSessionSchemaV1diff.txt
I have attached a patch(DERBY1706NPEwithSessionSchemaV1diff.txt) to this Jira
entry to fix the null
[ http://issues.apache.org/jira/browse/DERBY-1706?page=all ]
Mamta A. Satoor updated DERBY-1706:
---
Derby Info: [Patch Available]
NullPointerException occurs when trying to create a table in schema SESSION
[ http://issues.apache.org/jira/browse/DERBY-1707?page=all ]
Mamta A. Satoor updated DERBY-1707:
---
Derby Info: [Patch Available]
Specifying an incorrect optimizer property (constraint=null) gives
NullPointerException
Wrong results: duplicate rows returned for nested UNIONs when they should be
eliminated.
Key: DERBY-1852
URL: http://issues.apache.org/jira/browse/DERBY-1852
Laura Stewart wrote:
In the 10.2 Doc Review comments, there is a comment for the Reference
Manual that says:
Please add an example about the RESTRICT clause on REVOKE statements
for routines.
But refers to the GRANT Statement. The GRANT statement does not have
the RESTRICT clause for
[ http://issues.apache.org/jira/browse/DERBY-1852?page=all ]
A B updated DERBY-1852:
---
Attachment: d1852_quick_doNOTcommit.diff
Attaching a quick patch to fix this issue. I stumbled across this problem
while investigating DERBY-1777 and so I was able to tell
[
http://issues.apache.org/jira/browse/DERBY-1777?page=comments#action_12434780 ]
Bryan Pendleton commented on DERBY-1777:
Don't have much to offer, but I read the code and I read your writeup
and I don't see any improvements to suggest
Thanks, Kathey!
Kathey Marsden wrote:
Rick Hillegas wrote:
I would like to build a 10.2 release candidate once we remove the
following obstacles:
[snip obstacles]
I'd like to try to get DERBY-1547 in, it is really important to know
what version folks have.
Narayan posted a new patch. I
[
http://issues.apache.org/jira/browse/DERBY-1777?page=comments#action_12434795 ]
A B commented on DERBY-1777:
Not much of a review, know, but I did want to let you know that I did at
least this much of a review.
Thanks Bryan! Every little bit
[ http://issues.apache.org/jira/browse/DERBY-1706?page=all ]
Mamta A. Satoor updated DERBY-1706:
---
Attachment: DERBY1706NPEwithSessionSchemaV2diff.txt
I realized that I didn't change some of the println in the test case that I
added and hence
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas reopened DERBY-930:
-
Add support for autoloading of Derby client drivers
---
Key: DERBY-930
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Derby Info: [Existing Application Impact] (was: [Existing Application
Impact, Release Note Needed])
Since this issue was fixed, no release note is needed.
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
I would like to build a release candidate soon.
[snip]
Thanks for pointing this out. Yes, I am planning a mega-merge. So we're
down to one unreviewed/uncommitted patch: DERBY-1777.
Regards,
-Rick
Rick - there are several documentation
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas closed DERBY-930.
---
Resolution: Fixed
Add support for autoloading of Derby client drivers
---
Key: DERBY-930
Hi Laura,
Unless someone objects, I'll mega-merge tomorrow and then merge again
just before I build the release candidate.
Cheers,
-Rick
Laura Stewart wrote:
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
I would like to build a release candidate soon.
[snip]
Thanks for pointing
[ http://issues.apache.org/jira/browse/DERBY-1853?page=all ]
Rick Hillegas updated DERBY-1853:
-
Attachment: derby-1853-releaseNotes-v01.diff
RELEASE-NOTES.html
Attaching an attempt at mocking up this template. Also attaching a patch
[
http://issues.apache.org/jira/browse/DERBY-1706?page=comments#action_12434833 ]
Yip Ng commented on DERBY-1706:
---
Thanks for the additonal background information, Mamta. I have tried the
second patch DERBY1706NPEwithSessionSchemaV2diff.txt and
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Here are the note-needing issues:
DERBY-1130
Release note is in a comment for the issue:
http://issues.apache.org/jira/browse/DERBY-1130#action_12432244
DERBY-1103
I'll uncheck the release note needed from this issue as this was
included
[ http://issues.apache.org/jira/browse/DERBY-1103?page=all ]
Deepa Remesh reopened DERBY-1103:
-
Reopening to uncheck the release notes needed box. This was included in the
10.1.3 release notes.
Change the client driver to allow statements to
[ http://issues.apache.org/jira/browse/DERBY-1103?page=all ]
Deepa Remesh updated DERBY-1103:
Derby Info: (was: [Release Note Needed])
Change the client driver to allow statements to be garbage-collected once
they are not referenced in an
[ http://issues.apache.org/jira/browse/DERBY-1103?page=all ]
Deepa Remesh closed DERBY-1103.
---
Resolution: Fixed
Change the client driver to allow statements to be garbage-collected once
they are not referenced in an application
[
http://issues.apache.org/jira/browse/DERBY-1804?page=comments#action_12434842 ]
Susan Cline commented on DERBY-1804:
This patch looks good to me Laura. Although it still took me a while to
understand that table ;-) looking at it again.
Create a template for Release Notes for inclusion in our release distributions.
---
Key: DERBY-1853
URL: http://issues.apache.org/jira/browse/DERBY-1853
Project: Derby
[
http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434834 ]
Bryan Pendleton commented on DERBY-1326:
Hi Knut Anders, thanks for the clarifications. I am comfortable with your
explanation.
Network server may
On 9/14/06, Rick Hillegas [EMAIL PROTECTED] wrote:
Hi Laura,
Unless someone objects, I'll mega-merge tomorrow and then merge again
just before I build the release candidate.
Cheers,
-Rick
Laura Stewart wrote:
That is just great, I have a few doc patches that I am working on
based on the
[
http://issues.apache.org/jira/browse/DERBY-1588?page=comments#action_12434845 ]
Andrew McIntyre commented on DERBY-1588:
Could we link to the HTML instead of the PDFs, and make a separate link to the
PDF if you would like to keep the
The following issues are marked as needing release notes. However, I
can't find release notes attached to these issues. Could the owners of
these JIRAs help me find the missing release notes? More specifically,
could the owners do something like the following:
1) Toggle-off the release note
[
http://issues.apache.org/jira/browse/DERBY-928?page=comments#action_12434846 ]
Sunitha Kambhampati commented on DERBY-928:
---
Not quite sure if we want a release note for this new property that is being
added in 10.2, as this is
[
http://issues.apache.org/jira/browse/DERBY-1853?page=comments#action_12434850 ]
Andrew McIntyre commented on DERBY-1853:
Personally I would have put the Build Environment information at the end, since
I would consider the list of new
[
http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434851 ]
Deepa Remesh commented on DERBY-1326:
-
Thanks Knut for the answers. I still cannot wrap my head around old sessions
hanging around in the server. I think this
As some of you may have guessed, the email I sent out earlier with the
phrase meant to send to the list was *not* intended for this list.
My apologies, and please disregard.
Thanks,
David
[ http://issues.apache.org/jira/browse/DERBY-1839?page=all ]
Laura Stewart updated DERBY-1839:
-
Attachment: 1839_SQLstatements.diff
derby1839_SQLstatements_html.zip
Updated the SQL statements in the Reference Manual based on the
SYSCS_COMPRESS_TABLE corrupts table with a single column which is both a
primary key and a foreign key
--
Key: DERBY-1854
URL:
[
http://issues.apache.org/jira/browse/DERBY-1854?page=comments#action_12434856 ]
Chad Loder commented on DERBY-1854:
---
This may be similar to http://issues.apache.org/jira/browse/DERBY-1641, which
is still open.
SYSCS_COMPRESS_TABLE
David Van Couvering wrote:
As some of you may have guessed, the email I sent out earlier with the
phrase meant to send to the list was *not* intended for this list.
My apologies, and please disregard.
However, it does give us an interesting window into the planning that's
going on inside Sun
I'm trying to understand the expected behaviour of the assignment of
columns from an EOD SQL @Select to a data class using JavaBeans style
property accessors. I'm looking at section 19.1.5 User Class of JDBC 4.0.
I have a class similar to the example but a little different. The
difference is the
[ http://issues.apache.org/jira/browse/DERBY-1741?page=all ]
Andrew McIntyre resolved DERBY-1741.
Fix Version/s: 10.3.0.0
(was: 10.2.1.0)
Resolution: Fixed
Committed to trunk with revision 446527.
Remove the
81 matches
Mail list logo
