Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <380093409.1117743542496.JavaMail.jira@ajax.apache.org>
Date: Thu, 2 Jun 2005 22:19:02 +0200 (CEST)
From: "Samuel Andrew McIntyre (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED BY
 DEFAULT" column w/ Network Server
In-Reply-To: <999020150.1117129912716.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-318?page=all ]

Samuel Andrew McIntyre updated DERBY-318:
-----------------------------------------

    Fix Version: 10.1.0.0

> SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
> --------------------------------------------------------------------------
>
>          Key: DERBY-318
>          URL: http://issues.apache.org/jira/browse/DERBY-318
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions: 10.1.0.0
>  Environment: Derby in Network Server mode with either JCC or Derby Net Client.
>     Reporter: A B
>      Fix For: 10.1.0.0
>  Attachments: DERBY-318.patch, derbyall_diff.txt
>
> When connected to the Derby Network Server, if one has a table with a column defined as "GENERATED BY DEFAULT" and then one tries to select the "COLUMNDEFAULT" field from SYS.SYSCOLUMNS, the result is an NPE in the server code that leads to connection deallocation.
> I don't know if this is a problem with the "GENERATED BY DEFAULT" feature or if it's a problem with Network Server--more investigation is required.
> To reproduce, use ij to connect to a database using Network Server, and then:
> ij> create table t1 (i int generated by default as identity);
> 0 rows inserted/updated/deleted
> ij> select columndefault from sys.syscolumns;
> COLUMNDEFAULT
> ----------------------------------------------------------------------------------------------------
> ----------------------------
> null
> java.lang.NullPointerException
>         at org.apache.derby.impl.drda.DRDAConnThread.writeFdocaVal(DRDAConnThread.java:6550)
>         at org.apache.derby.impl.drda.DRDAConnThread.writeFDODTA(DRDAConnThread.java:5973)
>         at org.apache.derby.impl.drda.DRDAConnThread.writeQRYDTA(DRDAConnThread.java:5796)
>         at org.apache.derby.impl.drda.DRDAConnThread.processCommands(DRDAConnThread.java:595)
>         at org.apache.derby.impl.drda.DRDAConnThread.run(DRDAConnThread.java:226)
> agentThread[DRDAConnThread_2,5,main]
> ERROR 58009: Execution failed due to a distribution protocol error that caused deallocation of the conversation.  A DRDA Data Stream Syntax Error was detected.  Reason: 0x3

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira