[jira] Updated: (DERBY-638) Newtork driver setTransactionIsolation() causes a commit, but does not complete it locally

[ http://issues.apache.org/jira/browse/DERBY-638?page=all ] Bernt M. Johnsen updated DERBY-638: --- Summary: Newtork driver setTransactionIsolation() causes a commit, but does not complete it locally (was: setTransactionIsolation behaviour in network

[jira] Created: (DERBY-2064) Network client setTransactionIsolation() commits any active transactios

Network client setTransactionIsolation() commits any active transactios --- Key: DERBY-2064 URL: http://issues.apache.org/jira/browse/DERBY-2064 Project: Derby Issue Type:

[jira] Assigned: (DERBY-1770) Make mode db2sql an optional phrase in the create trigger statement

[ http://issues.apache.org/jira/browse/DERBY-1770?page=all ] Bernt M. Johnsen reassigned DERBY-1770: --- Assignee: Yip Ng (was: Bernt M. Johnsen) Since this will be fixed by DERBY-1953 and Yip is assigned to that one. Make mode db2sql an optional

[jira] Created: (DERBY-2065) Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction.

Network and embedded difference in SQLSTATE and message when Connection.close() with open transaction. -- Key: DERBY-2065 URL:

[jira] Updated: (DERBY-638) Network driver setTransactionIsolation() causes a commit, but does not complete it locally

[ http://issues.apache.org/jira/browse/DERBY-638?page=all ] Bernt M. Johnsen updated DERBY-638: --- Summary: Network driver setTransactionIsolation() causes a commit, but does not complete it locally (was: Newtork driver setTransactionIsolation() causes

Regression Test Report - tinderbox_trunk15 472803 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk15* 472803/2006-11-09 08:52:18 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 3519516 2 121.87% derbyall 020322032 0

[jira] Closed: (DERBY-2038) lang/releaseCompileLocks.sql and lang/closed.java fail under JDK 1.6 in insane mode

[ http://issues.apache.org/jira/browse/DERBY-2038?page=all ] Knut Anders Hatlen closed DERBY-2038. - Fix Version/s: 10.3.0.0 Resolution: Fixed Assignee: Knut Anders Hatlen Committed revision 472859. lang/releaseCompileLocks.sql and

Query regarding derby

Hi Derby Team, We are using derby database in our application. While updating the table, we are getting A lock could not be obtained within the time requested this exception. My queries are as follows 1. Why I am getting this exception? 2. What I should do to avoid this error? 3. How the

Regression Test Report - tinderbox_trunk15 472859 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk15* 472859/2006-11-09 12:02:30 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 3519516 2 121.59% derbyall 020322032 0

[jira] Commented: (DERBY-2042) Provide documentation for new RENAME COLUMN statement

[ http://issues.apache.org/jira/browse/DERBY-2042?page=comments#action_12448474 ] Knut Anders Hatlen commented on DERBY-2042: --- Thanks Bryan, I think the latest version looks good. Provide documentation for new RENAME COLUMN statement

[jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

[ http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12448487 ] Tomohito Nakayama commented on DERBY-1471: -- I found that it is needed to make server side implementation compatible with both of JDBC 4.0 and before that

Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

Tomohito Nakayama (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12448487 ] Tomohito Nakayama commented on DERBY-1471: -- I found that it is needed to make server side implementation compatible with

Re: Query regarding derby

Hi Sridharsingh, Please describe more your running configuration. This kind of error may occur if you are running different instances of derby to access a same database. Which version of derby are you running? Do you have more instances of derby on the same machine? What exactly are you

[jira] Commented: (DERBY-2063) derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with IBM JVM 142 and 15 on Linux platform

[ http://issues.apache.org/jira/browse/DERBY-2063?page=comments#action_12448491 ] Øystein Grøvlen commented on DERBY-2063: The tinderbox logs, indicates that these failures was introduced by the following check-in: Changes from

[jira] Commented: (DERBY-2056) junitTests/derbyNet/CompatibilityTest.java fails with IBM JVM 142 and 15 on both Windows and Linux platforms

[ http://issues.apache.org/jira/browse/DERBY-2056?page=comments#action_12448493 ] Øystein Grøvlen commented on DERBY-2056: The tinderbox logs indicates that this failure was introduced by one of the following check-ins (I think the most

[jira] Commented: (DERBY-2063) derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with IBM JVM 142 and 15 on Linux platform

[ http://issues.apache.org/jira/browse/DERBY-2063?page=comments#action_12448498 ] Daniel John Debrunner commented on DERBY-2063: -- So is the affects version incorrect, the change above was for the trunk 10.3, not the 10.2 branch,

Re: [jira] Commented: (DERBY-1471) Implement layer B streaming for new methods defined in JDBC4.0

Hello. Thank you for your kindness :) What is needed is calling method which was introduced in JDBC 4.0 from NetworkServer to utilize JDBC 4.0 feature in Engine. Concretely,the method is PreparedStatement#setBinaryStream(int, java.io.InputStream).

[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-2042 Provide documentation for new RENAME COLUMN statement http://issues.apache.org/jira/browse/DERBY-2042 DERBY-638 Network driver

[jira] Assigned: (DERBY-2063) derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with IBM JVM 142 and 15 on Linux platform

[ http://issues.apache.org/jira/browse/DERBY-2063?page=all ] Daniel John Debrunner reassigned DERBY-2063: Assignee: Daniel John Debrunner derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with IBM JVM 142 and 15 on Linux platform

Regression Test Report - Daily 472544 - Sun DBTG

[Auto-generated mail] *Daily* 472544/2006-11-08 18:00:09 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 7527520 099.37% derbyall F:1,E:061516150 0 105.87%

DDM object 0x1232 is not supported, DERBY-1326, DERBY-2063

I thought I would fix DERBY-2063 (ShutDownDBWhenNSShutsDownTest failing) by converting it to a standalone test using the client server decorator. Starting the with just the simple fixture testEngineShutdownDoesNotTakeDownNS I hit a network server/client bug that running the test through the

[jira] Resolved: (DERBY-2042) Provide documentation for new RENAME COLUMN statement

[ http://issues.apache.org/jira/browse/DERBY-2042?page=all ] Bryan Pendleton resolved DERBY-2042. Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed the new doc page to subversion as revision

Query plan extraction

Hi Derby community, a while ago I´ve posted some mails, which shortly introduced my extensions, which I`m developing during my thesis and which I want to contribute to the community. These extensions will extend Derby with kind of a persistent workload repository and a well-designed query

[jira] Updated: (DERBY-2063) derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with IBM JVM 142 and 15 on Linux platform

[ http://issues.apache.org/jira/browse/DERBY-2063?page=all ] Manjula Kutty updated DERBY-2063: - Affects Version/s: 10.3.0.0 (was: 10.2.1.8) Sysinfo: -- Java Information -- Java Version:

[jira] Created: (DERBY-2066) DisconnectException: The DDM object 0x1232 is not supported following shutdown of embedded engine while network server is running

DisconnectException: The DDM object 0x1232 is not supported following shutdown of embedded engine while network server is running - Key: DERBY-2066

[jira] Updated: (DERBY-2001) Add DITA templates for the 3 topic types into the trunk

[ http://issues.apache.org/jira/browse/DERBY-2001?page=all ] Laura Stewart updated DERBY-2001: - Attachment: derby2001_3.diff derby2001_3.stat Updated the templates per the lastest comments from Kim. Add DITA templates for the 3 topic

[jira] Created: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java - Key: DERBY-2067 URL: http://issues.apache.org/jira/browse/DERBY-2067 Project:

[jira] Updated: (DERBY-2001) Add DITA templates for the 3 topic types into the trunk

[ http://issues.apache.org/jira/browse/DERBY-2001?page=all ] Laura Stewart updated DERBY-2001: - Attachment: concept_template.dita reference_template.dita task_template.dita Please look at the dates on the template files.

[jira] Resolved: (DERBY-1980) Web site - Documentation - Add a new page with writing guidelines

[ http://issues.apache.org/jira/browse/DERBY-1980?page=all ] Laura Stewart resolved DERBY-1980. -- Resolution: Fixed Derby Info: (was: [Patch Available]) Web site - Documentation - Add a new page with writing guidelines

[jira] Closed: (DERBY-1980) Web site - Documentation - Add a new page with writing guidelines

[ http://issues.apache.org/jira/browse/DERBY-1980?page=all ] Laura Stewart closed DERBY-1980. The final patch #7 was committed and checked on the Web site. Additional Web site issues regarding documentation will need to be logged in a new JIRA issue. Web

[jira] Commented: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

[ http://issues.apache.org/jira/browse/DERBY-2067?page=comments#action_12448558 ] Knut Anders Hatlen commented on DERBY-2067: --- The assert failure is raised on a connection to a Derby instance which has been shut down. It is raised

[jira] Updated: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

[ http://issues.apache.org/jira/browse/DERBY-2067?page=all ] Knut Anders Hatlen updated DERBY-2067: -- Attachment: derby-2067.diff I propose that we change the assert in EmbedConnection.restoreContextStack() as suggested in the attached patch

[jira] Assigned: (DERBY-1645) ALTER TABLE ... SET INCREMENT BY X... Turns off the Generated By Default identity column constraint

[ http://issues.apache.org/jira/browse/DERBY-1645?page=all ] Bryan Pendleton reassigned DERBY-1645: -- Assignee: Bryan Pendleton ALTER TABLE ... SET INCREMENT BY X... Turns off the Generated By Default identity column constraint

[jira] Assigned: (DERBY-1495) Attempt to modify an identity column error after resetting identity column

[ http://issues.apache.org/jira/browse/DERBY-1495?page=all ] Bryan Pendleton reassigned DERBY-1495: -- Assignee: Bryan Pendleton Attempt to modify an identity column error after resetting identity column

Generated Docs - Working With Derby PDF

I am curious why the PDF version of Working With Derby is dated Oct 18, and the HTML Book version is dated Nov 3. I was under the impression that all of the Alpha docs were generated at the same time and frequently (nightly? weekly?) Can you please explain this to me? -- Laura Stewart

Re: Generated Docs - Working With Derby PDF

Laura Stewart wrote: I am curious why the PDF version of Working With Derby is dated Oct 18, and the HTML Book version is dated Nov 3. I was under the impression that all of the Alpha docs were generated at the same time and frequently (nightly? weekly?) Can you please explain this to me?

Re: (DERBY-378) implementing import/export of large objects...

Suresh Thalamati wrote: Hi Mike , After thinking bit more about the cases you mentioned, better solution might be to do write the binary data in HEX format when exporting the data to only one file, instead of modifying the binary data with double delimiters. This way main export file

Re: Query plan extraction

Felix Beyer wrote: Hi Derby community, Hello Felix! Good to see you back on the lists. While you were gone there was some discussion about the current state of Derby's query plan logging and I think it was generally agreed that it could use some improvement:

[jira] Created: (DERBY-2068) Misleading XJ004 exception when shutting down a database that is already shutdown.

Misleading XJ004 exception when shutting down a database that is already shutdown. -- Key: DERBY-2068 URL: http://issues.apache.org/jira/browse/DERBY-2068 Project: Derby

Regression Test Report - tinderbox_trunk15 473124 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk15* 473124/2006-11-09 23:52:18 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 1517516 2 120.86% derbyall 020342034 0

[jira] Created: (DERBY-2069) derby.system.bootAll=true only boots databases in the top level of the system directory

derby.system.bootAll=true only boots databases in the top level of the system directory --- Key: DERBY-2069 URL: http://issues.apache.org/jira/browse/DERBY-2069

Derby causes appserver hang with maxthreads

Hi, I am investigating an issue where Sun Application server hangs temporarily/permanently while talking to Derby Server. I could not reproduce the temporary hang. However I could make the hang permanent. Permanent Hang Steps : derby.properties will have the following settings:

[jira] Created: (DERBY-2070) Is there a way to initialise a BLOB in derby, and how to insert a document object in Derby

Is there a way to initialise a BLOB in derby, and how to insert a document object in Derby -- Key: DERBY-2070 URL: http://issues.apache.org/jira/browse/DERBY-2070

Regression Test Report - tinderbox_trunk15 473175 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk15* 473175/2006-11-10 04:42:18 CET Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* SunOS-5.10_i86pc-i386 1516515 2 121.16% derbyall 020402040 0

[jira] Updated: (DERBY-2067) Assert failure in EmbedConnection.restoreContextStack() when running lang/closed.java

[ http://issues.apache.org/jira/browse/DERBY-2067?page=all ] Knut Anders Hatlen updated DERBY-2067: -- Assignee: Knut Anders Hatlen Derby Info: [Patch Available] Assert failure in EmbedConnection.restoreContextStack() when running