[jira] Commented: (DERBY-1624) use of direct column name rather than alias make aggregation fail (Hibernate depends on that)

[ http://issues.apache.org/jira/browse/DERBY-1624?page=comments#action_12440038 ] Andrew McIntyre commented on DERBY-1624: Stumbled across this issue whilst searching for something else. Following Manish's query-rewriting example, the

[jira] Commented: (DERBY-737) SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they do not exist

[ http://issues.apache.org/jira/browse/DERBY-737?page=comments#action_12440039 ] Mamta A. Satoor commented on DERBY-737: --- I am slightly confused by the 1st line in the description of this Jira entry. It says There must be an entry in the

RE : Re: Classes diagram

Hi,I am developping some modifications of the code of apache derby, but the problem is that I don't have a global view of the sources of the database.I am looking for a diagram which will show me the classes and the links between them to know exactly where I must change the code, where I must add

Re: release endgame

On 10/4/06, Rick Hillegas [EMAIL PROTECTED] wrote: 2) Step (9) at http://www.apache.org/dev/mirror-step-by-step.html warns against using symbolic links in mirrored directories. But step (17) at http://wiki.apache.org/db-derby/DerbySnapshotOrRelease seems to indicate that we do use symbolic

Re: [VOTE] 10.2.1.6 release

Vote: +1, even though 'java.lang.OutOfMemoryError: PermGen space' occurred several times during the Large Data Volume DOTS/ATCJ2 test. My simple consistency checks did not reveal any problems. Large Data Volume tests on 10.2.1.6: - OS: Solaris 10 1/06 s10x_u1wos_19a X86 64bits

10.2.1.6 Large Data Volume OOME PermGen space issue

Ole Solberg wrote: [SNIP] *Saw 21 cases of java.lang.OutOfMemoryError: PermGen space during the ATCJ2 run.* First instance ~when backup starts. Appears to have the same signature as DERBY-210. I tried running the standalone repro I attached to DERBY-210, StatementStress.java, against

[jira] Commented: (DERBY-1902) Intermittent failures in predicatePushdown.sql

[ http://issues.apache.org/jira/browse/DERBY-1902?page=comments#action_12440142 ] Øystein Grøvlen commented on DERBY-1902: I turned the disk cache back on the Solaris x86 box, and the test still fails. (The test duration became

Re: Classes diagram

Julius Stroffek [EMAIL PROTECTED] writes: Hi Yann, I used a doxygen tool to generate a documentation (like javadoc). It has powerful capabilities to generate various graphs using graphviz (inheritance diagram, collaboration diagram, call graph, caller graph) with a source code included for

Re: Classes diagram

[EMAIL PROTECTED] writes: Any idea what is going on? Btw, how do I send a bug report? Ignore the last question. doxygen uses bugzilla. -- dt

DERBY-1434 - Client can send incorrect database name to server after having made multiple connections to different databases.

Hi All, I spend some time analyzing the communication protocol to find out something related to solution of DERBY-1434. Because I'm not familiar with the Derby communication protocol yet, I would like to get some advice. When client creates multiple connections to different databases

[jira] Commented: (DERBY-1902) Intermittent failures in predicatePushdown.sql

[ http://issues.apache.org/jira/browse/DERBY-1902?page=comments#action_12440163 ] A B commented on DERBY-1902: I turned the disk cache back on the Solaris x86 box, and the test still fails. Thanks for trying that out and for reporting the

Re: Classes diagram

Try the latest doxygen from cvs. I reported this to dimitri already. Latest version from cvs works fine. Regards Julo [EMAIL PROTECTED] wrote: Julius Stroffek [EMAIL PROTECTED] writes: Hi Yann, I used a doxygen tool to generate a documentation (like javadoc). It has powerful

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (14 issues) Subscriber: derby-dev Key Summary DERBY-1839 Doc Review Updates - Ref Manual http://issues.apache.org/jira/browse/DERBY-1839 DERBY-1847 SELECT statement asserts with XJ001 when attempted to

[jira] Updated: (DERBY-815) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

[ http://issues.apache.org/jira/browse/DERBY-815?page=all ] Dyre Tjeldvoll updated DERBY-815: - Assignee: (was: Dyre Tjeldvoll) Derby Info: (was: [Patch Available]) Removing patch available, since the latest patch no longer can be applied to

[jira] Updated: (DERBY-815) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

[ http://issues.apache.org/jira/browse/DERBY-815?page=all ] Dyre Tjeldvoll updated DERBY-815: - Fix Version/s: 10.3.0.0 (was: 10.2.2.0) Prevent unneeded object creation and excessive decoding in parseSQLDTA_work()

[jira] Updated: (DERBY-737) SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they do not exist

[ http://issues.apache.org/jira/browse/DERBY-737?page=all ] Mike Matrigali updated DERBY-737: - I believe your interpretation is correct. The request is to always update statistics when running the compress table command. Internally this may mean

[jira] Assigned: (DERBY-1785) junit tests fail with permission access problems when run with j9 jvms

[ http://issues.apache.org/jira/browse/DERBY-1785?page=all ] Myrna van Lunteren reassigned DERBY-1785: - Assignee: Myrna van Lunteren junit tests fail with permission access problems when run with j9 jvms

[jira] Commented: (DERBY-1785) junit tests fail with permission access problems when run with j9 jvms

[ http://issues.apache.org/jira/browse/DERBY-1785?page=comments#action_12440184 ] Myrna van Lunteren commented on DERBY-1785: --- I'm assigning this to me because I keep forgetting the number. If someone else feels interest, be welcome

[jira] Updated: (DERBY-1894) SQLSTATE 42X10 occurs when qualifying a column with a synonym in ORDER BY clause

[ http://issues.apache.org/jira/browse/DERBY-1894?page=all ] Mike Matrigali updated DERBY-1894: -- Fix Version/s: 10.2.2.0 backported fix from trunk to 10.2.1.7 (version does not exist in jira right now - so marked fixed in 10.2.2) SQLSTATE 42X10

[junit] Making progess faster towards a pure Junit world

I'd like to make progress faster towards a pure JUnit set of tests for Derby but I believe the fact we need to setup the tests and the JUnit utility classes to run under the harness slows down progress as well as adding complications. An example of how it slows down is that any change to a

building the release page

I'm working on creating the release page for 10.2.1.6. I'm afraid I don't understand the following paragraph from step (18) on http://wiki.apache.org/db-derby/DerbySnapshotOrRelease: the HTML comments which constitute the form template into which the mirrors.cgi script splices in the mirror

Re: building the release page

On 10/5/06, Rick Hillegas [EMAIL PROTECTED] wrote: the HTML comments which constitute the form template into which the mirrors.cgi script splices in the mirror information will be removed by Forrest. It is necessary to add these comments back in to the release page before committing or letting

[jira] Created: (DERBY-1931) Derby JAR files should be grouped as a single library in Package Explorer

Derby JAR files should be grouped as a single library in Package Explorer - Key: DERBY-1931 URL: http://issues.apache.org/jira/browse/DERBY-1931 Project: Derby Issue

[jira] Commented: (DERBY-1785) junit tests fail with permission access problems when run with j9 jvms

[ http://issues.apache.org/jira/browse/DERBY-1785?page=comments#action_12440223 ] Daniel John Debrunner commented on DERBY-1785: -- I thought the following approach would work when running the tests directlly. Set up the

[jira] Created: (DERBY-1932) Reference Manual updates - JDBC Reference section

Reference Manual updates - JDBC Reference section - Key: DERBY-1932 URL: http://issues.apache.org/jira/browse/DERBY-1932 Project: Derby Issue Type: Bug Components: Documentation

[jira] Commented: (DERBY-1785) junit tests fail with permission access problems when run with j9 jvms

[ http://issues.apache.org/jira/browse/DERBY-1785?page=comments#action_12440229 ] Daniel John Debrunner commented on DERBY-1785: -- Adding this (dummy) properties on the command line stopped the parsing problem and allowed me to run

[jira] Created: (DERBY-1933) Reference Manual updates - Setting attributes for the db connection URL

Reference Manual updates - Setting attributes for the db connection URL --- Key: DERBY-1933 URL: http://issues.apache.org/jira/browse/DERBY-1933 Project: Derby Issue Type:

[jira] Created: (DERBY-1934) Reference Manual updates - J2EE Compliance: Java Transaction API and javax.sql Extensions

Reference Manual updates - J2EE Compliance: Java Transaction API and javax.sql Extensions - Key: DERBY-1934 URL: http://issues.apache.org/jira/browse/DERBY-1934

[jira] Created: (DERBY-1935) Reference Manual - Derby Limitations

Reference Manual - Derby Limitations Key: DERBY-1935 URL: http://issues.apache.org/jira/browse/DERBY-1935 Project: Derby Issue Type: Bug Components: Documentation Affects Versions: 10.2.1.6

[jira] Created: (DERBY-1936) Create sample application that demonstrates Derby running offline in browser and synchronizing with backend

Create sample application that demonstrates Derby running offline in browser and synchronizing with backend --- Key: DERBY-1936 URL:

[jira] Updated: (DERBY-1847) SELECT statement asserts with XJ001 when attempted to select a newly added column in SQL authorization mode

[ http://issues.apache.org/jira/browse/DERBY-1847?page=all ] Mike Matrigali updated DERBY-1847: -- Fix Version/s: 10.3.0.0 committed patch to the trunk and marked fixed in 10.3. m3_ibm142:148svn commit Sending

Re: logQueryPlan readability

Bryan Pendleton wrote: I was thinking that there might be some smaller, easier, things that we could do which would offer some smaller wins, but might still be worth it. Thanks for taking an interest in this discussion, Bryan, and for writing-up some ideas! I think that if these smaller

[jira] Created: (DERBY-1937) Website page incorrecly lists Derby versioning (in one spot) as Minor.major

Website page incorrecly lists Derby versioning (in one spot) as Minor.major --- Key: DERBY-1937 URL: http://issues.apache.org/jira/browse/DERBY-1937 Project: Derby

Proposal - Doc Process Improvements

Hi I've been working on updates to the Derby docs for a few months, and now that we are close to completing this release I think that this is a good time to revisit the processes (and stumbling blocks) that the Derby project has for updating and reviewing the Derby documentation. Here is what I

[jira] Updated: (DERBY-1936) Create sample application that demonstrates Derby running offline in browser and synchronizing with backend

[ http://issues.apache.org/jira/browse/DERBY-1936?page=all ] David Van Couvering updated DERBY-1936: --- Attachment: localcal.diff Here is the patch. Given that this example is not included in the build or tests and the example's build.xml puts the

[jira] Updated: (DERBY-1732) The language and store systems treat a JVM error such as OutOfMemoryError differently leading to the raw store protocol violation errors

[ http://issues.apache.org/jira/browse/DERBY-1732?page=all ] Daniel John Debrunner updated DERBY-1732: - Derby Info: (was: [Patch Available]) Patch Committed revision 453395 - Thanks Sunitha. The language and store systems treat a JVM error

[jira] Closed: (DERBY-1904) COALESCE with NULL parameter problem

[ http://issues.apache.org/jira/browse/DERBY-1904?page=all ] Dag H. Wanvik closed DERBY-1904. Resolution: Invalid Closing as agreed, not a bug. COALESCE with NULL parameter problem Key:

[jira] Created: (DERBY-1938) Add support for setObject(col, null)

Add support for setObject(col, null) --- Key: DERBY-1938 URL: http://issues.apache.org/jira/browse/DERBY-1938 Project: Derby Issue Type: Improvement Components: JDBC Reporter: Dag

[jira] Updated: (DERBY-1938) Add support for setObject(arg, null)

[ http://issues.apache.org/jira/browse/DERBY-1938?page=all ] Dag H. Wanvik updated DERBY-1938: - Summary: Add support for setObject(arg, null) (was: Add support for setObject(col, null)) Add support for setObject(arg, null)

[jira] Assigned: (DERBY-1397) Tuning Guide: Puzzling optimizer documentation

[ http://issues.apache.org/jira/browse/DERBY-1397?page=all ] Laura Stewart reassigned DERBY-1397: Assignee: (was: Laura Stewart) Unassigning myself from this issue for now. Unable to work on it for 10.2. Tuning Guide: Puzzling optimizer

[jira] Reopened: (DERBY-1791) Make policy file and harness tests cope with derbyTesting being in a different folder (test) to the other jars.

[ http://issues.apache.org/jira/browse/DERBY-1791?page=all ] Daniel John Debrunner reopened DERBY-1791: -- See about 50 test failures running the tests using the layout in the 10.2.1.6 release. Make policy file and harness tests cope

[jira] Resolved: (DERBY-1489) Provide ALTER TABLE DROP COLUMN functionality

[ http://issues.apache.org/jira/browse/DERBY-1489?page=all ] Bryan Pendleton resolved DERBY-1489. Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Thanks very much to all the reviewers, and particularly

[jira] Updated: (DERBY-1819) couple of small errors in the admin guide documnetation of NetworkServerControl() API (shutdown and sysinfo ...)

[ http://issues.apache.org/jira/browse/DERBY-1819?page=all ] Laura Stewart updated DERBY-1819: - Attachment: derby1819_1.diff derby1819_html1.zip Updated the files per the comments and reworked the index entries: The files are:

[jira] Updated: (DERBY-1819) couple of small errors in the admin guide documnetation of NetworkServerControl() API (shutdown and sysinfo ...)

[ http://issues.apache.org/jira/browse/DERBY-1819?page=all ] Laura Stewart updated DERBY-1819: - Fix Version/s: 10.2.2.0 Affects Version/s: 10.2.1.6 couple of small errors in the admin guide documnetation of NetworkServerControl() API

[jira] Updated: (DERBY-1819) couple of small errors in the admin guide documnetation of NetworkServerControl() API (shutdown and sysinfo ...)

[ http://issues.apache.org/jira/browse/DERBY-1819?page=all ] Laura Stewart updated DERBY-1819: - Derby Info: [Patch Available] couple of small errors in the admin guide documnetation of NetworkServerControl() API (shutdown and sysinfo ...)

[jira] Assigned: (DERBY-1240) creating /restoring a db from backup using createFrom with log at different location copies the log from backup to the db dir also.

[ http://issues.apache.org/jira/browse/DERBY-1240?page=all ] Suresh Thalamati reassigned DERBY-1240: --- Assignee: Suresh Thalamati creating /restoring a db from backup using createFrom with log at different location copies the log from backup to

[RESULT] [VOTE] 10.2.1.6 release

Thanks for everyone's hard work on coding, documenting, and testing 10.2.1. The polls have closed. The community has approved 10.2.1.6 as an official Derby release: +1: Laura Stewart Jean Andersen (pmc) Andrew McIntyre (pmc) Rick Hillegas (pmc) Knut Anders Hatlen (pmc) Mike Matrigali (pmc)

Re: [RESULT] [VOTE] 10.2.1.6 release

Whohoo! Congratulations, everyone, for an amazing process, all your hard work, and a 10.2 release! David On 10/5/06, Rick Hillegas [EMAIL PROTECTED] wrote: Thanks for everyone's hard work on coding, documenting, and testing 10.2.1. The polls have closed. The community has approved 10.2.1.6 as

[jira] Updated: (DERBY-1860) Create release notes for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1860?page=all ] Rick Hillegas updated DERBY-1860: - Attachment: derby-1860-releasePage-v01.diff Commit derby-1860-releasePage-v01.diff. This introduces a 10.2.1.6 release page and wires it into the download

[jira] Commented: (DERBY-1860) Create release notes for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1860?page=comments#action_12440297 ] Rick Hillegas commented on DERBY-1860: -- Previous patch committed at subversion revision 453434. Create release notes for 10.2 -

EoD removed from JDBC 4 !!!

http://weblogs.java.net/blog/lancea/archive/2006/10/jdbc_eod_api_de.html So I assume we will have to make changes to trunk and 10.2 branch to allow Derby to build against JDK 6 (mustang) build 101. Dan.

Re: EoD removed from JDBC 4 !!!

Hi Dan, After I make these changes, I think it would make sense for me to post a 10.2.1 snapshot which reflects the altered api. For the moment, I think we have to avoid the latest build (build 101) of the 1.6 jdk. Regards, -Rick Daniel John Debrunner wrote: