[
https://issues.apache.org/jira/browse/DERBY-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415510#comment-13415510
]
Mamta A. Satoor commented on DERBY-5407:
----------------------------------------
I did further debugging of this issue and I found that we are sending the
correct information over the wire for the network server.
This is where we write the column data on the server side
Thread [DRDAConnThread_11] (Suspended)
TypeDescriptorImpl.writeExternal(ObjectOutput) line: 549
ObjectOutputStream.writeExternalData(Externalizable) line: 1449
ObjectOutputStream.writeOrdinaryObject(Object, ObjectStreamClass,
boolean) line: 1418
ObjectOutputStream.writeObject0(Object, boolean) line: 1178
ObjectOutputStream.writeObject(Object) line: 347
DDMWriter.writeUDT(Object, int) line: 1181
DRDAConnThread.writeFdocaVal(int, Object, int, int, int, boolean,
DRDAStatement, boolean) line: 8072
DRDAConnThread.writeFDODTA(DRDAStatement) line: 7256
DRDAConnThread.writeQRYDTA(DRDAStatement) line: 6990
DRDAConnThread.processCommands() line: 910
DRDAConnThread.run() line: 295
And this is where we read the column data on the client side
Thread [main] (Suspended)
BaseTypeIdImpl.getTypeFormatId() line: 258
BaseTypeIdImpl.toParsableString(TypeDescriptor) line: 178
TypeDescriptorImpl.getSQLstring() line: 441
TypeDescriptorImpl.toString() line: 446
NetCursor(Cursor).getString(int) line: 1061
NetResultSet40(ResultSet).getString(int) line: 1069
JDBCDisplayUtil.DisplayRow(PrintWriter, ResultSet, ResultSetMetaData,
int, Vector, Connection, int, int[], int[]) line: 693
JDBCDisplayUtil.indent_DisplayResults(PrintWriter, List, Connection,
int, int[], int[]) line: 385
JDBCDisplayUtil.indent_DisplayResults(PrintWriter, ResultSet,
Connection, int, int[], int[]) line: 338
JDBCDisplayUtil.indent_DisplayResults(PrintWriter, Statement,
Connection, int, int[], int[]) line: 241
JDBCDisplayUtil.DisplayResults(PrintWriter, Statement, Connection)
line: 229
utilMain.displayResult(LocalizedOutput, ijResult, Connection) line: 454
utilMain.doCatch(String) line: 528
utilMain.runScriptGuts() line: 369
utilMain.go(LocalizedInput[], LocalizedOutput) line: 245
Main.go(LocalizedInput, LocalizedOutput) line: 229
Main.mainCore(String[], Main) line: 184
Main.main(String[]) line: 75
ij.main(String[]) line: 59
I think I should know in a day or two as to what is happening.
> When run across the network, dblook produces unusable DDL for VARCHAR FOR BIT
> DATA columns.
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-5407
> URL: https://issues.apache.org/jira/browse/DERBY-5407
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.8.1.2
> Reporter: Rick Hillegas
> Assignee: Mamta A. Satoor
> Labels: derby_triage10_9
> Attachments: SystemCatalogTest.java
>
>
> In private correspondence, Mani Afschar Yazdi reports that dblook omits the
> length specification for VARCHAR FOR BIT DATA columns when run across the
> network. Embedded dblook runs fine. I can reproduce this problem as follows:
> 1) Bring up a server (here I am using port 8246).
> 2) Create a database with the following ij script:
> connect 'jdbc:derby://localhost:8246/memory:db;create=true';
> create table t( a varchar( 20 ) for bit data );
> 3) Now run dblook across the network:
> java -org.apache.derby.tools.dblook -d "jdbc:derby://localhost:8246/memory:db"
> This produces the following DDL for the table:
> CREATE TABLE "APP"."T" ("A" VARCHAR () FOR BIT DATA);
> A similar experiment using an embedded database produces usable DDL which
> includes a length specification for the VARCHAR FOR BIT DATA column.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
