Return-Path: 
 <derby-dev-return-7102-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 46170 invoked from network); 29 Jul 2005 02:37:09 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 29 Jul 2005 02:37:09 -0000
Received: (qmail 50005 invoked by uid 500); 29 Jul 2005 02:37:08 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 49970 invoked by uid 500); 29 Jul 2005 02:37:07 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-dev-help@db.apache.org>
list-unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 49957 invoked by uid 99); 29 Jul 2005 02:37:07 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2005 19:37:07 -0700
X-ASF-Spam-Status: No, hits=0.4 required=10.0
	tests=SPF_HELO_FAIL
X-Spam-Check-By: apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Received: from [32.97.110.130] (HELO e32.co.us.ibm.com) (32.97.110.130)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2005 19:36:59 -0700
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
 [9.17.195.106])
	by e32.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j6T2b3kQ710554
	for <derby-dev@db.apache.org>; Thu, 28 Jul 2005 22:37:04 -0400
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com
 [9.17.195.168])
	by d03relay04.boulder.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id
 j6T2b7b4190568
	for <derby-dev@db.apache.org>; Thu, 28 Jul 2005 20:37:07 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j6T2b3TA030069
	for <derby-dev@db.apache.org>; Thu, 28 Jul 2005 20:37:03 -0600
Received: from [127.0.0.1] (sig-9-48-120-147.mts.ibm.com [9.48.120.147])
	by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j6T2awVN029929
	for <derby-dev@db.apache.org>; Thu, 28 Jul 2005 20:37:02 -0600
Message-ID: <42E9964C.7060502@debrunners.com>
Date: Thu, 28 Jul 2005 19:37:00 -0700
From: Daniel John Debrunner <djd@debrunners.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: JDBCDisplayUtil column name truncation
References: <42E9094C.9060802@acadiau.ca> <42E98220.20103@Sourcery.Org>
In-Reply-To: <42E98220.20103@Sourcery.Org>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Satheesh Bandaram wrote:

> May be JDBCDisplayUtil could use setMinDisplayWidth() and
> implementation, much like what it already supports using
> setMaxDisplayWidth(). IJ currently uses this setMaxDisplayWidth() to
> support 'maximumDisplayWidth <num>' directive.

Or rather than another configuration parameter, just by default make
the column width big enough to display the column's display name.
So the display width would be:

   MAX(column display name width, column width)

Dan.

> 
> Satheesh
> 
> Philip Wilder wrote:
> 
> 
>>This is something of a trivial issue but has anyone else ever been
>>irked by the the JDBCDisplayUtil habit of cutting off column names for
>>small columns? I was doing some work today where it was a hinderance
>>and I was wondering if anyone else had ever felt the same way. After
>>looking at the code a change looks like it would be reasonably simple...