Received: from kodu.home.ee (isdn-54.uninet.ee [194.204.0.118]) by hub.org (8.9.3/8.9.3) with ESMTP id DAA32011 for ; Tue, 3 Aug 1999 03:45:04 -0400 (EDT) (envelope-from hannu@trust.ee) Received: from trust.ee (hannu@localhost [127.0.0.1]) by kodu.home.ee (8.8.7/8.8.7) with ESMTP id KAA00493; Tue, 3 Aug 1999 10:43:16 +0300 Sender: hannu@kodu.home.ee Message-ID: <37A69D94.330E098A@trust.ee> Date: Tue, 03 Aug 1999 10:43:16 +0300 From: Hannu Krosing Organization: Trust-O-Matic =?iso-8859-1?Q?O=DC?= X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.2.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Ross J. Reedstrom" CC: jens@jens.de, pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] sigh .. another bug in the JDBC driver (ResultSetMetaData.getColumnDisplaySize) References: <19990802131200.A15411@wallace.ece.rice.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Ross J. Reedstrom" wrote: > > On Mon, Aug 02, 1999 at 07:23:07PM +0000, Jens Glaser wrote: > > Hi, > > > > here's just another annoying bug in the JDBC driver: > > > > ResultSetMetaData.getColumnDisplaySize() returns the length of the > > *column label*, but it is expected to return the max width of the column! > > > > Hmm, the Zope Python interface suffers from the same problem (and the > same work around): lack of column width info, substituting the column > label length. I'm not sure that this info is available through libpq but it appeared at least to protocol level in about 6.4 for variable length fields (it has always been there for fixed width of course). At least ODBC drivers do use it. ------- Hannu