Derby
  1. Derby
  2. DERBY-5407

When run across the network, dblook produces unusable DDL for VARCHAR FOR BIT DATA columns.

    Details

    • Urgency:
      Normal
    • Issue & fix info:
      Repro attached
    • Bug behavior facts:
      Embedded/Client difference, Seen in production

      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.

      1. SystemCatalogTest.java
        32 kB
        Mamta A. Satoor
      2. DERBY5407_patch1_diff.txt
        6 kB
        Mamta A. Satoor

        Issue Links

          Activity

            People

            • Assignee:
              Mamta A. Satoor
              Reporter:
              Rick Hillegas
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development