Re: NullPointerException in derby

Peter Nabbefeld schrieb: [EMAIL PROTECTED] schrieb: Peter Nabbefeld <[EMAIL PROTECTED]> writes: Hello, I've got the following NPE: java.lang.NullPointerException at org.apache.derby.impl.sql.catalog.SYSSTATEMENTSRowFactory.makeSYSSTATEMENTSrow(Unknown Source) at org.apac

Re: [jira] Commented: (DERBY-339) Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be deferred to the server.

Hi Kathey, First of all, let me admit, I am no XA expert but here are my comments on the review package anyways.(I used the patch attached to the Jira. That's the latest patch, correct?) 1)I noticed that you added a new sql state to SqlState.java as follows+ public final static SqlState CANNOT_CLOS

[jira] Closed: (DERBY-227) Reference manual has incorrect information for supported resultset types for prepareCall JDBC api

[ http://issues.apache.org/jira/browse/DERBY-227?page=all ] Jeff Levitt closed DERBY-227: - Fixed in 10.1.0.0 > Reference manual has incorrect information for supported resultset types for > prepareCall JDBC api > --

[jira] Closed: (DERBY-181) Function/Procedure specific name documented but not supported

[ http://issues.apache.org/jira/browse/DERBY-181?page=all ] Jeff Levitt closed DERBY-181: - Fixed in 10.1.0.0 > Function/Procedure specific name documented but not supported > - > > Key: D

[jira] Closed: (DERBY-52) Cannot create CHAR column with size greater than 254

[ http://issues.apache.org/jira/browse/DERBY-52?page=all ] Jeff Levitt closed DERBY-52: Fixed in 10.1.0.0 > Cannot create CHAR column with size greater than 254 > > > Key: DERBY-52 > UR

Re: [PATCH] Add "if (SanityManager.DEBUG)" around two unprotected uses of SanityManager.

Simple, but useful patch. Commited. Satheesh Sending    java\engine\org\apache\derby\iapi\sql\dictionary\ColumnDescriptor.java Sending    java\engine\org\apache\derby\impl\store\raw\data\FileContainer.java Transmitting file data .. Committed revision 188643. Army wrote: There are two

[PATCH] Add "if (SanityManager.DEBUG)" around two unprotected uses of SanityManager.

There are two files in the codline that use SanityManager without first checking to see if the compiler is running in SANE mode. This means that when the code is built in INSANE mode, the references to SanityManager will still exist in the compiled class file, which is wrong. Attached is a ve

[jira] Closed: (DERBY-234) Documentation of DateTime types is incomplete

[ http://issues.apache.org/jira/browse/DERBY-234?page=all ] Jeff Levitt closed DERBY-234: - Fixed in 10.1.0.0 > Documentation of DateTime types is incomplete > - > > Key: DERBY-234 > URL: http://

[jira] Closed: (DERBY-168) Can't ALTER a column to have a new DEFAULT value.

[ http://issues.apache.org/jira/browse/DERBY-168?page=all ] Jeff Levitt closed DERBY-168: - Fixed in 10.1.0.0 > Can't ALTER a column to have a new DEFAULT value. > - > > Key: DERBY-168 > URL:

[jira] Closed: (DERBY-164) unicodeEscape command in ij doesn't work

[ http://issues.apache.org/jira/browse/DERBY-164?page=all ] Jeff Levitt closed DERBY-164: - Fixed in 10.1.0.0 > unicodeEscape command in ij doesn't work > > > Key: DERBY-164 > URL: http://issues.apa

[jira] Closed: (DERBY-116) Content comment for SYSTRIGGERS.TRIGGERDEFINITION is misleading

[ http://issues.apache.org/jira/browse/DERBY-116?page=all ] Jeff Levitt closed DERBY-116: - Fixed in 10.1.0.0 > Content comment for SYSTRIGGERS.TRIGGERDEFINITION is misleading > --- > > Ke

[jira] Created: (DERBY-342) ERROR 42818: Comparisons between 'LONG VARCHAR' and 'CHAR' are not supported

ERROR 42818: Comparisons between 'LONG VARCHAR' and 'CHAR' are not supported Key: DERBY-342 URL: http://issues.apache.org/jira/browse/DERBY-342 Project: Derby Type: Bug Components: JDBC, T

[jira] Closed: (DERBY-235) unable to create a database using a different storage factory than the one provided by default with the engine

[ http://issues.apache.org/jira/browse/DERBY-235?page=all ] Suresh Thalamati closed DERBY-235: -- > unable to create a database using a different storage factory than the one > provided by default with the engine > --

[jira] Closed: (DERBY-96) partial log record writes that occur because of out-of order writes need to be handled by recovery.

[ http://issues.apache.org/jira/browse/DERBY-96?page=all ] Suresh Thalamati closed DERBY-96: - > partial log record writes that occur because of out-of order writes need to > be handled by recovery. >

[jira] Closed: (DERBY-101) Limit on Number of log that can be created should be increased (current limit is 4194303)

[ http://issues.apache.org/jira/browse/DERBY-101?page=all ] Suresh Thalamati closed DERBY-101: -- > Limit on Number of log that can be created should be increased (current limit > is 4194303) > --

[jira] Updated: (DERBY-341) Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained

[ http://issues.apache.org/jira/browse/DERBY-341?page=all ] Kathey Marsden updated DERBY-341: - Fix Version: 10.2.0.0 (was: 10.1.0.0) Version: 10.1.0.0 (was: 10.2.0.0) > Client should disallow XAConnection

[jira] Updated: (DERBY-341) Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained

[ http://issues.apache.org/jira/browse/DERBY-341?page=all ] Kathey Marsden updated DERBY-341: - Version: 10.2.0.0 (was: 10.1.0.0) Moving to 10.2 > Client should disallow XAConnection getConnection() when a global transaction > has been

[jira] Commented: (DERBY-341) Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained

[ http://issues.apache.org/jira/browse/DERBY-341?page=comments#action_12312805 ] Kathey Marsden commented on DERBY-341: -- Looking briefly at this issue I see that NetConnection.flowReconnect does not actually flow anything, but rather sets up a cache of

IRC Chat about DERBY-243 connection toString should uniquely identify the connection

David and I had the following chat on IRC kmarsden: So I just wanted to clarify with all the traffic back and forth on this issue. As I understand it ... kmarsden: 1) The derby.log and ErrorLogVTI go back to the old format kmarsden: 2) Connection.toString() prints the SESSION_ID that prints in t

[jira] Closed: (DERBY-340) Update plugin_howto.xml under the Integration tab for the Derby web site

[ http://issues.apache.org/jira/browse/DERBY-340?page=all ] Susan Cline closed DERBY-340: - Thanks for committing the changes to the integrate/plugin_howto.xml file. > Update plugin_howto.xml under the Integration tab for the Derby web site > --

[jira] Commented: (DERBY-277) Group By and TRIM do not cooperate with more than 1 'not like' statement

[ http://issues.apache.org/jira/browse/DERBY-277?page=comments#action_12312794 ] Peter Haighton commented on DERBY-277: -- Hi, Here is the Schema, CREATE TABLE NA ( NAID BIGINT GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1) CON

[jira] Commented: (DERBY-339) Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be deferred to the server.

[ http://issues.apache.org/jira/browse/DERBY-339?page=comments#action_12312792 ] Kathey Marsden commented on DERBY-339: -- Note: The XA+ specification can be found at: http://www.opengroup.org/bookstore/catalog/s423.htm > Network client XA should only k

[jira] Updated: (DERBY-341) Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained

[ http://issues.apache.org/jira/browse/DERBY-341?page=all ] Andrew McIntyre updated DERBY-341: -- Fix Version: 10.1.0.0 > Client should disallow XAConnection getConnection() when a global transaction > has been started and a logical connection has alread

[jira] Updated: (DERBY-339) Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be deferred to the server.

[ http://issues.apache.org/jira/browse/DERBY-339?page=all ] Andrew McIntyre updated DERBY-339: -- Fix Version: 10.1.0.0 > Network client XA should only keep XA state for transaction branch > association, to track whether to send commit in autocommit mode

[jira] Resolved: (DERBY-246) XA end() fails with Connection is closed error

[ http://issues.apache.org/jira/browse/DERBY-246?page=all ] Kathey Marsden resolved DERBY-246: -- Fix Version: 10.1.0.0 Resolution: Fixed The fix for this issue was checked in. r179867 | kmarsden | 2005-06-03 12:35:33 -0700 (Fri, 03 Jun 2005) |

Re: DERBY-147 - how do I know if it is part of 10.1 or any other release ?

Anyone has any cycles to work with or independently on Derby-147? The bug is easily reproducable and has a patch done by Bernd. But the patch needs some adjustment to make it complete, specifically, it should not allow ORDER BY on an alias, if the SELECT list has multiple references to the same ali

[jira] Resolved: (DERBY-340) Update plugin_howto.xml under the Integration tab for the Derby web site

[ http://issues.apache.org/jira/browse/DERBY-340?page=all ] Jean T. Anderson resolved DERBY-340: Resolution: Fixed Committed Susan Clines's patch, revision 180458, that modifies integrate/plugin_howto.html to clarify which Eclipse releases can

[jira] Closed: (DERBY-14) Triggers do not evaluate functions in VALUES trigger actions.

[ http://issues.apache.org/jira/browse/DERBY-14?page=all ] Jack Klebanoff closed DERBY-14: --- > Triggers do not evaluate functions in VALUES trigger actions. > - > > Key: DERBY-14 >

[jira] Commented: (DERBY-339) Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be deferred to the server.

[ http://issues.apache.org/jira/browse/DERBY-339?page=comments#action_12312783 ] Kathey Marsden commented on DERBY-339: -- The patch for this issue contains some non active changes for DERBY-341 in ClientXAConnection.java. Those changes can be ignored fo

Re: 10.1 release status

Andrew McIntyre wrote: >Comments and suggestions greatly appreciated. If you see anything >missing from this list, please let me know! > > > I plan to check in DERBY-339 (patch under review) and hopefully DERBY-341 today. DERBY-339 is I think a show stopper for XA. Kathey

[jira] Assigned: (DERBY-340) Update plugin_howto.xml under the Integration tab for the Derby web site

[ http://issues.apache.org/jira/browse/DERBY-340?page=all ] Jean T. Anderson reassigned DERBY-340: -- Assign To: Jean T. Anderson > Update plugin_howto.xml under the Integration tab for the Derby web site >

[jira] Updated: (DERBY-339) Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be deferred to the server.

[ http://issues.apache.org/jira/browse/DERBY-339?page=all ] Kathey Marsden updated DERBY-339: - Summary: Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state

[jira] Updated: (DERBY-340) Update plugin_howto.xml under the Integration tab for the Derby web site

[ http://issues.apache.org/jira/browse/DERBY-340?page=all ] Susan Cline updated DERBY-340: -- Attachment: plugin_howto.diff Attached is plugin_howto.diff which contains the updated comments for the plugin_howto.xml file. svn diff was run from the trunk/src/d

[jira] Created: (DERBY-341) Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained

Client should disallow XAConnection getConnection() when a global transaction has been started and a logical connection has already been obtained -

[jira] Created: (DERBY-340) Update plugin_howto.xml under the Integration tab for the Derby web site

Update plugin_howto.xml under the Integration tab for the Derby web site Key: DERBY-340 URL: http://issues.apache.org/jira/browse/DERBY-340 Project: Derby Type: Task Components: Web Site

[jira] Commented: (DERBY-150) Disable logging

[ http://issues.apache.org/jira/browse/DERBY-150?page=comments#action_12312757 ] Andrew McIntyre commented on DERBY-150: --- I think this may be a duplicate of DERBY-218. It would be nice if the submitter of this issue could determine if the reduced dura

[jira] Assigned: (DERBY-337) dblook doesn't generate SQL statements for SQL functions.

[ http://issues.apache.org/jira/browse/DERBY-337?page=all ] A B reassigned DERBY-337: - Assign To: A B > dblook doesn't generate SQL statements for SQL functions. > - > > Key: DERBY-337 > U

Re: 10.1 release status

Andrew McIntyre wrote: Hello derby-dev, Here's the current status as we head towards a 10.1 release. [ snip ] Derby-337: dblook should generate SQL statements for SQL functions - any takers? Unless anyone objects, I'll volunteer to look at this one... Army

[jira] Assigned: (DERBY-217) issue with BLOBs and batch updates in 10.1.0.0

[ http://issues.apache.org/jira/browse/DERBY-217?page=all ] Satheesh Bandaram reassigned DERBY-217: --- Assign To: Satheesh Bandaram > issue with BLOBs and batch updates in 10.1.0.0 > -- > > Key: DE

Re: NullPointerException in derby

[EMAIL PROTECTED] schrieb: Peter Nabbefeld <[EMAIL PROTECTED]> writes: Hello, I've got the following NPE: java.lang.NullPointerException at org.apache.derby.impl.sql.catalog.SYSSTATEMENTSRowFactory.makeSYSSTATEMENTSrow(Unknown Source) at org.apache.derby.impl.sql.catalog.Dat

Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection

Thanks for this very careful review, Oystein. Responses below. Øystein Grøvlen wrote: "DVC" == David Van Couvering <[EMAIL PROTECTED]> writes: DVC> Hi, Kathey. Nobody has tested this patch. I think it's ready to go, DVC> but the last patch I did with a full derbyall that then res

[jira] Created: (DERBY-339) Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be defered to the server.

Network client XA should only keep XA state for transaction branch association, to track whether to send commit in autocommit mode. All other state and state related decisions should be defered to the server. ---

Re: NullPointerException in derby

Peter Nabbefeld <[EMAIL PROTECTED]> writes: > Hello, > > I've got the following NPE: > > java.lang.NullPointerException > at > org.apache.derby.impl.sql.catalog.SYSSTATEMENTSRowFactory.makeSYSSTATEMENTSrow(Unknown > Source) > at > org.apache.derby.impl.sql.catalog.DataDictionaryI

[jira] Closed: (DERBY-127) Aliased Columns not recognized after "group by... order by" combination

[ http://issues.apache.org/jira/browse/DERBY-127?page=all ] Jack Klebanoff closed DERBY-127: > Aliased Columns not recognized after "group by... order by" combination > --- > >

[jira] Closed: (DERBY-6) Trigger of the form: create trigger ... values myFunction(); has no effect.

[ http://issues.apache.org/jira/browse/DERBY-6?page=all ] Jack Klebanoff closed DERBY-6: -- > Trigger of the form: create trigger ... values myFunction(); has no effect. > --- > >

DERBY-213 Cleanup

Hello Kathey, Here are the changes we discussed in our last IRC conversation. The only change I have that strikes me as kind of ugly is Step 5 but if need be we can move the setting of the default qryclsimp value to the constructors. To anyone else reading this, I'm not posting this to JIRA t

Re: [jira] Commented: (DERBY-150) Disable logging

Øystein Grøvlen wrote: "AH(" == Amit Handa (JIRA) writes: AH(> [ http://issues.apache.org/jira/browse/DERBY-150?page=comments#action_12312720 ] AH(> Amit Handa commented on DERBY-150: AH(> -- AH(> To further work on this topic

[jira] Closed: (DERBY-320) Failed test: derbyall/derbynetclientmats/derbynetmats.fail:lang/updatableResultSet.java

[ http://issues.apache.org/jira/browse/DERBY-320?page=all ] Bernt M. Johnsen closed DERBY-320: -- Verified on revision 180256M: Java Version:1.5.0_03 Java Vendor: Sun Microsystems Inc. OS name: Linux OS architecture: i386 OS version:

[jira] Commented: (DERBY-273) The derbynet/dataSourcePermissions_net.java test fails intermittently

[ http://issues.apache.org/jira/browse/DERBY-273?page=comments#action_12312740 ] Tomohito Nakayama commented on DERBY-273: - I have started to survey ... My first question was "What is ShutdownException ?" JavaDoc told "A ShutdownException is a run

Re: [jira] Commented: (DERBY-150) Disable logging

> "AH(" == Amit Handa (JIRA) writes: AH(> [ http://issues.apache.org/jira/browse/DERBY-150?page=comments#action_12312720 ] AH(> Amit Handa commented on DERBY-150: AH(> -- AH(> To further work on this topic there are two things AH(> 1

[jira] Closed: (DERBY-230) "Schema already exists" when creating a table

[ http://issues.apache.org/jira/browse/DERBY-230?page=all ] Øystein Grøvlen closed DERBY-230: - > "Schema already exists" when creating a table > - > > Key: DERBY-230 > URL: http://issues.apac

[jira] Resolved: (DERBY-230) "Schema already exists" when creating a table

[ http://issues.apache.org/jira/browse/DERBY-230?page=all ] Øystein Grøvlen resolved DERBY-230: --- Resolution: Fixed > "Schema already exists" when creating a table > - > > Key: DERBY-230 >

Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection

> "DVC" == David Van Couvering <[EMAIL PROTECTED]> writes: DVC> Hi, Kathey. Nobody has tested this patch. I think it's ready to go, DVC> but the last patch I did with a full derbyall that then resulted in a DVC> bunch of failures for Dan indicates we really need somebody else t

Re: store/OnlineCompressTest.java fails on Linux-2.4.20-31.9 i686-i686 (RedHat 9)

Mike Matrigali wrote: I believe svn 180008 should correct this problem, but I was never able to exactly reproduce your error - I didn't make it to a linux machine. I believe the problem was a timing related error where the system was sometimes incorrectly reading past end of file. On my machine

[jira] Commented: (DERBY-150) Disable logging

[ http://issues.apache.org/jira/browse/DERBY-150?page=comments#action_12312720 ] Amit Handa commented on DERBY-150: -- To further work on this topic there are two things 1. To identify a test case that logging consumes time cycles. 2. And if logging is turn