[DERBY-5407] When run across the network, dblook produces unusable DDL for VARCHAR FOR BIT DATA columns.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.1.2
• Fix Version/s: 10.6.2.4, 10.7.1.4, 10.8.3.0, 10.9.2.2, 10.10.1.1
• Component/s: Tools
• Labels: derby_backport_reject_10_5
• Urgency: Normal
• Issue & fix info: Repro attached
• Bug behavior facts: Embedded/Client difference, Seen in production
• Assignee: Mamta A. Satoor
• Reporter: Richard N. Hillegas
• Created: 12/Sep/11 13:50
• Updated: 14/Jun/13 17:22
• Resolved: 25/Jul/12 18:30

Description

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.

Issue Links

• is related to: DERBY-5852 dblook fails with client if derby.jar is not in classpath with java.sql.SQLException: Error marshalling or unmarshalling a user defined type