Re: Porting Derby Database files between machines

On 4/27/06, Jean T. Anderson <[EMAIL PROTECTED]> wrote: > Geoff Powdrell wrote: > > Hi, > > I would like to know if the derby database files can be moved between > > machines. That when you create a derby database that there is no registry > > settings made or machine specific settings applied to

Review of Derby's JDBC4 implementation

See http://binkley.blogspot.com/2006/04/nifty-jdbc-40.html What I liked: "everything worked!" David

[jira] Commented: (DERBY-1129) compatibility tests fail with security related errors.

[ http://issues.apache.org/jira/browse/DERBY-1129?page=comments#action_12376875 ] Kathey Marsden commented on DERBY-1129: --- >From the description of this issue it sounds like a pretty serious regression >on 3/17. I was wondering if anyojne has looked i

Re: Porting Derby Database files between machines

Geoff Powdrell wrote: > Hi, > I would like to know if the derby database files can be moved between > machines. That when you create a derby database that there is no registry > settings made or machine specific settings applied to that machine. > > For example : > If I have a database which I c

[jira] Commented: (DERBY-805) Push join predicates into union and other set operations. DERBY-649 implemented scalar (single table) predicate pushdown. Adding join predicate push down could improve pe

[ http://issues.apache.org/jira/browse/DERBY-805?page=comments#action_12376859 ] Satheesh Bandaram commented on DERBY-805: - I have committed this patch to 10.1 branch. Thanks for pulling all relavent checkins. > Push join predicates into union and

[jira] Commented: (DERBY-85) NPE when creating a trigger on a table and default schema doesn't exist.

[ http://issues.apache.org/jira/browse/DERBY-85?page=comments#action_12376858 ] Satheesh Bandaram commented on DERBY-85: I think it would be great to port this fix to 10.1 branch. I have seen some users hit this problem. Dyre, do you happen to have

Re: Binding votes for a release (was Re: 10.2 release in August?)

Michelle Caisse wrote: > Jean T. Anderson wrote: >> Michelle Caisse wrote: >> Probably it's time to discuss clarifying the DB PMC docs with the DB >> PMC. Since you're on the DB PMC, I'd encourage you to go ahead and >> initiate that discussion. >> > I agree, and I will do that. And I meant to

Re: Binding votes for a release (was Re: 10.2 release in August?)

Jean T. Anderson wrote: Michelle Caisse wrote: ... ready to be released". The Apache guidelines do not cover a vote on a release plan, but the Apache DB site does: "Lazy majority decides each issue in a release plan." Again, according to I think "lazy majority" in thi

10.1.3 Bug Fixing

Hello Derby-Dev! I put up a Wiki page http://wiki.apache.org/db-derby/TenOneThreeRelease with bug fixing info for the release.Here is our (pretty tight) schedule according to Andrew, our release manager: Last day to commit changes:June 8 Testing and voting beginsJune 9 Ta

Re: Binding votes for a release (was Re: 10.2 release in August?)

Michelle Caisse wrote: > I want to clarify that the current discussion is about a release plan, > not a release, so the issue of PMC binding votes is moot for now. It's Yes, that's correct. That's why I changed the subject from "Re: 10.2 release in August?" to "Binding votes for a release". Somet

[jira] Commented: (DERBY-1263) build.xml doesn't create the ${basedir}/src/dtd directory

[ http://issues.apache.org/jira/browse/DERBY-1263?page=comments#action_12376855 ] Jean T. Anderson commented on DERBY-1263: - I wonder if you need to configure jEdit to resolve the DITA DTDs locally. The forrest web site has instructions for resolvin

Porting Derby Database files between machines

Hi, I would like to know if the derby database files can be moved between machines. That when you create a derby database that there is no registry settings made or machine specific settings applied to that machine. For example : If I have a database which I connect to via the url 'jdbc:derby:te

[jira] Commented: (DERBY-1263) build.xml doesn't create the ${basedir}/src/dtd directory

[ http://issues.apache.org/jira/browse/DERBY-1263?page=comments#action_12376854 ] Andrew McIntyre commented on DERBY-1263: You need to point jEdit to DITA's XML catalog. See: See http://forrest.apache.org/docs_0_70/catalog.html#jedit for instructi

[jira] Commented: (DERBY-1263) build.xml doesn't create the ${basedir}/src/dtd directory

[ http://issues.apache.org/jira/browse/DERBY-1263?page=comments#action_12376853 ] Halley Pacheco de Oliveira commented on DERBY-1263: --- The absence of dtd directory doesn't cause any failure in doc building, but when I open any .dita file t

Re: Binding votes for a release (was Re: 10.2 release in August?)

I want to clarify that the current discussion is about a release plan, not a release, so the issue of PMC binding votes is moot for now.  It's my understanding that a release vote is a vote "on whether a package is ready to be released".  The Apache guidelines do not cover a vote on a release p

[jira] Resolved: (DERBY-1197) Problem while setting NULL in PreparedSattement for java.sql.Types.Integer

[ http://issues.apache.org/jira/browse/DERBY-1197?page=all ] Kathey Marsden resolved DERBY-1197: --- Resolution: Invalid User indicated we could mark this resolved as it was user error but it might be good to open a doc issue for this. > Problem wh

[jira] Commented: (DERBY-1254) XAConnection uses NetConnection as underlying physical connection for JDBC4/Java 1.6

[ http://issues.apache.org/jira/browse/DERBY-1254?page=comments#action_12376843 ] Rick Hillegas commented on DERBY-1254: -- This patch simplifies the creation of JDBC4 NetConnections. JDBC4 tests run cleanly. Derbyall runs cleanly modulo wisconsin noise.

[jira] Commented: (DERBY-1007) Optimizer can return incorrect "best cost" estimates with nested subqueries, which leads to generation of sub-optimal plans.

[ http://issues.apache.org/jira/browse/DERBY-1007?page=comments#action_12376837 ] A B commented on DERBY-1007: While waiting for the followup patch to be committed to 10.2 (trunk), I've also included the patch to port these changes (the original plus the follow

[jira] Commented: (DERBY-1073) Reset optimizer timeout for subqueries on a per-round basis to allow consideration of plans that use pushed predicates.

[ http://issues.apache.org/jira/browse/DERBY-1073?page=comments#action_12376834 ] A B commented on DERBY-1073: Timeout fix was committed with svn revision 393608. Patch to port these changes to 10.1 is attached to DERBY-805 and also posted here: http://articl

[jira] Updated: (DERBY-805) Push join predicates into union and other set operations. DERBY-649 implemented scalar (single table) predicate pushdown. Adding join predicate push down could improve perf

[ http://issues.apache.org/jira/browse/DERBY-805?page=all ] A B updated DERBY-805: -- Attachment: d805_1007_1073_portTo10_1.patch d805_1007_1073_portTo10_1.stat Attaching patch to port all phases of this issue plus changes for DERBY-1007 and DERBY-10

Re: [Db-derby Wiki] Update of "HighValueFixCandidates" by KatheyMarsden

Bryan Pendleton wrote: >> The following page has been changed by KatheyMarsden: >> http://wiki.apache.org/db-derby/HighValueFixCandidates > > > > I am interested in porting some trunk fixes to 10.1.3, specifically: > - DERBY-125 > - DERBY-170 > - DERBY-491 > Hey, that's great! > Is there a che

[jira] Commented: (DERBY-1263) build.xml doesn't create the ${basedir}/src/dtd directory

[ http://issues.apache.org/jira/browse/DERBY-1263?page=comments#action_12376830 ] Andrew McIntyre commented on DERBY-1263: It was determined recently that because the DITA toolkit uses an XML catalog, the location of the DTDs are determined by corre

[jira] Updated: (DERBY-900) Remove use of String(byte[]) and String(byte[], int, int) constructors in network client leading to non-portable behaviour

[ http://issues.apache.org/jira/browse/DERBY-900?page=all ] Sunitha Kambhampati updated DERBY-900: -- Attachment: derby900.p2_encodingChange.diff.txt I am dividing the Derby900.p2.diff.txt into two separate patches after talking to kathey. This pa

Re: [Db-derby Wiki] Update of "HighValueFixCandidates" by KatheyMarsden

The following page has been changed by KatheyMarsden: http://wiki.apache.org/db-derby/HighValueFixCandidates I am interested in porting some trunk fixes to 10.1.3, specifically: - DERBY-125 - DERBY-170 - DERBY-491 Is there a checklist or simple summary of the mechanics of doing this? I assu

[jira] Updated: (DERBY-1079) Build javadoc under jdk 1.6

[ http://issues.apache.org/jira/browse/DERBY-1079?page=all ] Rick Hillegas updated DERBY-1079: - Attachment: bug1079_clientPublicAPI.diff Committed bug1079_clientPublicAPI.diff at subversion revision 397650. This adds javadoc to our public JDBC4 classes

[jira] Created: (DERBY-1263) build.xml doesn't create the ${basedir}/src/dtd directory

build.xml doesn't create the ${basedir}/src/dtd directory --- Key: DERBY-1263 URL: http://issues.apache.org/jira/browse/DERBY-1263 Project: Derby Type: Bug Environment: DITA-sourced documentation Reporte

Re: 10.2 release in August?

Andreas Korneliussen <[EMAIL PROTECTED]> writes: [snip] > +1 > > Yes, I think we do have many new features, which are independent from > JDBC 4 (i.e SUR), and it would be good to get them released to users. +1 I also feel that there are enough new features to warrant a new feature release fairly

Binding votes for a release (was Re: 10.2 release in August?)

actually, there's a good thread on legal-discuss regarding this topic starting at: http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200511.mbox/[EMAIL PROTECTED] and for anyone's email client that wraps the previous line: http://tinyurl.com/nunu8 -jean Jean T. Anderson wrote: >

Resetting Statement and poolability

Hi, In the client code (am directory) Statments (and PreparedStatements and CallableStatements) can be reset (that is; they have various resetXXX methods). When are statements reset? Jdbc4 introduces the isPoolable attribute that has a default value (false for Statement, true for the derived clas

[jira] Updated: (DERBY-1090) Implement Connection.isValid as defined by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1090?page=all ] Olav Sandstaa updated DERBY-1090: - Derby Info: [Patch Available] > Implement Connection.isValid as defined by JDBC4 > > > Key: DERBY-10

[jira] Updated: (DERBY-1090) Implement Connection.isValid as defined by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1090?page=all ] Olav Sandstaa updated DERBY-1090: - Attachment: client1090_patch2.diff This patch (client1090_patch2.diff) addresses the problem of Connection.isValid() hanging infinite if the server is either

[jira] Updated: (DERBY-862) Clean up the big pile of javadoc warnings for the derbydocs target and make derbydocs run under jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-862?page=all ] Rick Hillegas updated DERBY-862: Attachment: bug862_misc4.diff Committed bug862_misc4.diff at subversion revision 397624. Miscellaneous javadoc warnings in the following classes: Sending

Re: JIRA popular issues tab does not show all issues with a vote

On 4/27/06, Kathey Marsden <[EMAIL PROTECTED]> wrote: > Andrew McIntyre wrote: > > > <>I think it only displays the top 50. I'm guessing that in our case it > > fills out the list to 50 with whatever the first issues retrieved from > > the database with 1 vote happen to be. > > > It would be great

Re: JIRA popular issues tab does not show all issues with a vote

Andrew McIntyre wrote: > <>I think it only displays the top 50. I'm guessing that in our case it > fills out the list to 50 with whatever the first issues retrieved from > the database with 1 vote happen to be. > It would be great to have finer granularity on the vote reporting. In addition to wa

Re: 10.2 release in August?

Michelle Caisse wrote: > Jean T. Anderson wrote: > >> One clarifying procedural note ... voting guidelines for releases are >> here: >> >> http://www.apache.org/foundation/voting.html#ReleaseVotes >> >> A release requires three binding +1 votes -- db pmc votes are binding >> for derby. A -1 expres

[jira] Commented: (DERBY-1254) XAConnection uses NetConnection as underlying physical connection for JDBC4/Java 1.6

[ http://issues.apache.org/jira/browse/DERBY-1254?page=comments#action_12376790 ] Rick Hillegas commented on DERBY-1254: -- I'm running tests against this patch now. > XAConnection uses NetConnection as underlying physical connection for > JDBC4/Java 1.

Re: 10.2 release in August?

Jean T. Anderson wrote: One clarifying procedural note ... voting guidelines for releases are here: http://www.apache.org/foundation/voting.html#ReleaseVotes A release requires three binding +1 votes -- db pmc votes are binding for derby. A -1 expresses an opinion, but can't actually veto a re

[jira] Updated: (DERBY-1148) Client XA getTransactionIsolation() does not return the correct isolation level when rejoining a global transaction

[ http://issues.apache.org/jira/browse/DERBY-1148?page=all ] Deepa Remesh updated DERBY-1148: Attachment: XACheckIsolation.java Kathey mentioned the problem could be in reporting of isolation level by client. So I was trying to check that the isolation

[jira] Resolved: (DERBY-903) Remove use of String(byte[]) and String(byte[], int, int) constructors in testing leading to non-portable behaviour

[ http://issues.apache.org/jira/browse/DERBY-903?page=all ] Myrna van Lunteren resolved DERBY-903: -- Resolution: Fixed Derby Info: (was: [Patch Available]) > Remove use of String(byte[]) and String(byte[], int, int) constructors in > test

[jira] Closed: (DERBY-1247) test DerbyNetAutoStart uses non-portable mechanism to check on derby.log

[ http://issues.apache.org/jira/browse/DERBY-1247?page=all ] Myrna van Lunteren closed DERBY-1247: - > test DerbyNetAutoStart uses non-portable mechanism to check on derby.log >

[jira] Resolved: (DERBY-1247) test DerbyNetAutoStart uses non-portable mechanism to check on derby.log

[ http://issues.apache.org/jira/browse/DERBY-1247?page=all ] Myrna van Lunteren resolved DERBY-1247: --- Resolution: Fixed > test DerbyNetAutoStart uses non-portable mechanism to check on derby.log > --

[jira] Updated: (DERBY-1007) Optimizer can return incorrect "best cost" estimates with nested subqueries, which leads to generation of sub-optimal plans.

[ http://issues.apache.org/jira/browse/DERBY-1007?page=all ] Mike Matrigali updated DERBY-1007: -- I have reviewed the BackingStoreHashtable.java changes, and they look ok to me. As the comments mention it is wierd to compare row count and memory size, but

Re: 10.2 release in August?

Knut Anders Hatlen wrote: <>Satheesh Bandaram <[EMAIL PROTECTED]> writes: Thanks for the update, Satheesh. Does this mean that an earlier release would have to back out or disable parts of your code, or could we keep them as undocumented features? Don't think keeping them undocumented i

[jira] Updated: (DERBY-1259) Optimizer plan consideration doesn't account for infinite cost estimates and can therefore choose plans requiring excessive memory.

[ http://issues.apache.org/jira/browse/DERBY-1259?page=all ] Mike Matrigali updated DERBY-1259: -- At least in the 10.2 development line, I believe we should fix this issue and then address the fallout as necessary. It seems reasonable not to change the qu

[jira] Closed: (DERBY-73) Ability to compile under JDK1.5

[ http://issues.apache.org/jira/browse/DERBY-73?page=all ] Andrew McIntyre closed DERBY-73: > Ability to compile under JDK1.5 > --- > > Key: DERBY-73 > URL: http://issues.apache.org/jira/browse/DERBY-73 >

[jira] Resolved: (DERBY-73) Ability to compile under JDK1.5

[ http://issues.apache.org/jira/browse/DERBY-73?page=all ] Andrew McIntyre resolved DERBY-73: -- Resolution: Fixed Assign To: Andrew McIntyre Fixed by changes to DERBY-1078 > Ability to compile under JDK1.5 > --- > >

Re: Commit patch for DERBY-326 (Re: [jira] Updated: (DERBY-326) Improve streaming of large objects for network server and client)

TomohitoNakayama wrote: > Hello. > > I will commit this patch, seeing no one point out anything in days ... > Thank you Naka for your steadfast work on this important issue. I have been doing less and less in the DRDA rhelm lately so won't be reviewing but hope others get a chance to do that eit

Re: JIRA popular issues tab does not show all issues with a vote

On 4/27/06, Deepa Remesh <[EMAIL PROTECTED]> wrote: > Hi, > > I was looking at the popular issues tab in JIRA > (http://issues.apache.org/jira/browse/DERBY?report=com.atlassian.jira.plugin.system.project:popularissues-panel) > Some of the issues I voted for (e.g. DERBY-210) does not show up in > th

JIRA popular issues tab does not show all issues with a vote

Hi, I was looking at the popular issues tab in JIRA (http://issues.apache.org/jira/browse/DERBY?report=com.atlassian.jira.plugin.system.project:popularissues-panel) Some of the issues I voted for (e.g. DERBY-210) does not show up in this tab. The heading for the tab mentions this: Popular Issues

[jira] Assigned: (DERBY-1258) Wrong value returned in a row trigger action statement if the table has column names that are identical when upper-cased.

[ http://issues.apache.org/jira/browse/DERBY-1258?page=all ] Daniel John Debrunner reassigned DERBY-1258: Assign To: Daniel John Debrunner > Wrong value returned in a row trigger action statement if the table has > column names that are iden

Re: Regression flag: unset if fixed?

Andrew McIntyre wrote: >Hi derby-dev, > > That issue covered a regression, but I fixed the issue. It's >now closed, but should we clear the regression flag since there is no >longer a regression? > > I prefer to keep it so we can track the number of regressions that have occurred and fixed. Be

[jira] Resolved: (DERBY-1039) Database creation should fail if specified log device path already exists

[ http://issues.apache.org/jira/browse/DERBY-1039?page=all ] Mike Matrigali resolved DERBY-1039: --- Fix Version: 10.2.0.0 10.1.3.0 10.1.2.4 Resolution: Fixed > Database creation should fail if specified log dev

[jira] Updated: (DERBY-1039) Database creation should fail if specified log device path already exists

[ http://issues.apache.org/jira/browse/DERBY-1039?page=all ] Mike Matrigali updated DERBY-1039: -- backported the fix for this issue into the 10.1 branch, targeted for the 10.1.3 release: m101_142:20>svn commit Sendingjava\engine\org\apache\derby\i

[jira] Commented: (DERBY-900) Remove use of String(byte[]) and String(byte[], int, int) constructors in network client leading to non-portable behaviour

[ http://issues.apache.org/jira/browse/DERBY-900?page=comments#action_12376759 ] Sunitha Kambhampati commented on DERBY-900: --- The non portable String.getBytes() is used in parseSQLDCGRP as explained earlier. This method is called by parseSQLDCROW

[jira] Commented: (DERBY-822) Client driver: Pre-fetch data on executeQuery()

[ http://issues.apache.org/jira/browse/DERBY-822?page=comments#action_12376757 ] Kathey Marsden commented on DERBY-822: -- I noticed that on the day of this checkin, lang/simpleScroll.sql, and lang/scrollCursors1.sql with JCC 2.5 (56) started failing w

[jira] Updated: (DERBY-1254) XAConnection uses NetConnection as underlying physical connection for JDBC4/Java 1.6

[ http://issues.apache.org/jira/browse/DERBY-1254?page=all ] V.Narayanan updated DERBY-1254: --- Attachment: DERBY_1254.diff DERBY_1254.stat The getNetXAConnection method overriden in NetXAConnection40 has a different signature from the super

[jira] Updated: (DERBY-941) Add JDBC4 support for Statement Events

[ http://issues.apache.org/jira/browse/DERBY-941?page=all ] V.Narayanan updated DERBY-941: -- Attachment: statementeventlisteners_client_v1.diff statementeventlisteners_client_v1.stat Hi, Thank you for the thorough and detail review of the pat

Question about Datasource methods in embedded and client driver

Hi, When writing a testcase, I noticed that Derby client driver's DataSource classes do not have methods like setCreateDatabase and setShutdownDatabase whereas embedded driver has these methods. Embedded driver also has an additional set method "setAttributesAsPassword" which I think is planned to

[jira] Updated: (DERBY-1235) Move isPoolable() and setPoolable() from PreparedStatement to Statement

[ http://issues.apache.org/jira/browse/DERBY-1235?page=all ] Dyre Tjeldvoll updated DERBY-1235: -- Derby Info: (was: [Patch Available]) > Move isPoolable() and setPoolable() from PreparedStatement to Statement > -

Re: 10.2 release in August?

Satheesh Bandaram wrote: > If there is a good chance of Mustang and JDBC4 being ready by Sept/Oct, we > should avoid another release in August. Rick doesn't seem to foresee a > Mustang schedule slip and given > incomplete nature of Grant & Revoke authorization, I vote to keep one > release in Sep/

Commit patch for DERBY-326 (Re: [jira] Updated: (DERBY-326) Improve streaming of large objects for network server and client)

Hello. I will commit this patch, seeing no one point out anything in days ... Best regards. Tomohito Nakayama (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-326?page=all ] Tomohito Nakayama updated DERBY-326: Attachment: DERBY-326_7.pa

Re: 10.2 release in August?

Andrew McIntyre <[EMAIL PROTECTED]> writes: > On 4/26/06, Knut Anders Hatlen <[EMAIL PROTECTED]> wrote: >> A bug-fix release on the 10.1 branch is very good for Derby in my >> opinion, but I would also really like to see that we got all the new >> features out to our users. >> >> I would therefore

[jira] Assigned: (DERBY-1254) XAConnection uses NetConnection as underlying physical connection for JDBC4/Java 1.6

[ http://issues.apache.org/jira/browse/DERBY-1254?page=all ] V.Narayanan reassigned DERBY-1254: -- Assign To: V.Narayanan > XAConnection uses NetConnection as underlying physical connection for > JDBC4/Java 1.6 > -

Re: 10.2 release in August?

Satheesh Bandaram <[EMAIL PROTECTED]> writes: > Daniel John Debrunner wrote: > > Knut Anders Hatlen wrote: > > August 1: Release Apache Derby 10.2.1.0. > > Obviously, the dates need to be aligned with the 10.1.3 schedule. > > Is this something the co

[jira] Created: (DERBY-1262) Like-predicates: % does not match tab character

Like-predicates: % does not match tab character --- Key: DERBY-1262 URL: http://issues.apache.org/jira/browse/DERBY-1262 Project: Derby Type: Bug Components: SQL Versions: 10.0.2.0 Environment: Embedded, Solar

[jira] Created: (DERBY-1261) Two triggers on same table cause "ERROR 54038: Maximum depth of nested triggers was exceeded."

Two triggers on same table cause "ERROR 54038: Maximum depth of nested triggers was exceeded." -- Key: DERBY-1261 URL: http://issues.apache.org/jira/browse/DERBY-1261 Project: Derby

Re: 10.2 release in August?

"Jean T. Anderson" <[EMAIL PROTECTED]> writes: > What features would you like to see released in August that you don't > think could wait for an October release? It is not a single feature, but the set of new features that is interesting. I have been in contact with users who are very eager to se

Regression Test Failure! - Derby 397252 - Sun DBTG

[Auto-generated mail] *Derby* 397252/2006-04-26 19:46:14 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 128668540 0 105.41% SunOS-5.10_i86pc-i386 Details in http://www.multinet.no/

[jira] Closed: (DERBY-1236) Verify that applications can't manipulate the transaction state while inside a distributed transaction.

[ http://issues.apache.org/jira/browse/DERBY-1236?page=all ] Dyre Tjeldvoll closed DERBY-1236: - > Verify that applications can't manipulate the transaction state while inside > a distributed transaction. > --

[jira] Commented: (DERBY-1235) Move isPoolable() and setPoolable() from PreparedStatement to Statement

[ http://issues.apache.org/jira/browse/DERBY-1235?page=comments#action_12376674 ] Knut Anders Hatlen commented on DERBY-1235: --- Hi Dyre, I see this diff in the jdbc40 suite (DerbyNetClient): * Diff file jdbc40/DerbyNetClient/jdbc40/TestPre