[ http://issues.apache.org/jira/browse/DERBY-318?page=all ]
Tomohito Nakayama updated DERBY-318:
------------------------------------
Attachment: derbyall_diff.txt
Test result of previous uploaded 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: 10.1.0.0
> 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;
> 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
