Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27F649B71 for ; Wed, 18 Jul 2012 17:17:35 +0000 (UTC) Received: (qmail 45686 invoked by uid 500); 18 Jul 2012 17:17:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 45655 invoked by uid 500); 18 Jul 2012 17:17:34 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 45643 invoked by uid 99); 18 Jul 2012 17:17:34 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2012 17:17:34 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 88D83142856 for ; Wed, 18 Jul 2012 17:17:34 +0000 (UTC) Date: Wed, 18 Jul 2012 17:17:34 +0000 (UTC) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Message-ID: <353396303.69993.1342631854563.JavaMail.jiratomcat@issues-vm> In-Reply-To: <520811362.17181.1315835469193.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (DERBY-5407) When run across the network, dblook produces unusable DDL for VARCHAR FOR BIT DATA columns. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417265#comment-13417265 ] Mike Matrigali commented on DERBY-5407: --------------------------------------- fix looks good to me. Is this bug a regression, if so any idea what version/change caused it? > 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: DERBY5407_patch1_diff.txt, 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