db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohito Nakayama (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-318) SYS.SYSCOLUMN problem with "GENERATED BY DEFAULT" column w/ Network Server
Date Thu, 02 Jun 2005 10:26:53 GMT
     [ http://issues.apache.org/jira/browse/DERBY-318?page=all ]

Tomohito Nakayama updated DERBY-318:

    Attachment: DERBY-318.patch

if the SYSCOLUMNS record stands for default autoinc column.
Test for 1: was added to lang/syscat.sql.
lang/syscat.sql became to executed in derbynetmats.runall.
This results addition of syscat.sql to both of derbynet and derbynetclient.

Executed derbyall and found three error.

They seems to be same error as next.

Test result will be uploaded next to this patch.

> 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:
>  Environment: Derby in Network Server mode with either JCC or Derby Net Client.
>     Reporter: A B
>  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;
> ----------------------------------------------------------------------------------------------------
> ----------------------------
> 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:
For more information on JIRA, see:

View raw message