From: Bruce Momjian <maillist@candle.pha.pa.us>
To: hannu@trust.ee
Cc: byronn@insightdist.com
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] Re: [INTERFACES] retrieving varchar size
Date: Thu, 23 Apr 1998 12:45:42 -0400 (EDT)
Message-ID: <199804231645.MAA26157@candle.pha.pa.us> (raw)
In-Reply-To: <353F6BBC.50EB8C99@sid.trust.ee>
>
> Byron Nikolaidis wrote:
> >
> > Hello,
> >
> > I was wondering if it would be possible, in the Postgres backend, to
> > send back the defined column size for the varchar data type (and
> > possibly the char() type, i.e., bpchar) on a query? Currently, it just
> > sends back -1 for the size, which makes it difficult in the frontend
> > (i.e., odbc driver) to determine what the size of the column is.
>
> While the right solution to this is of course getting the size from
> backend, there exists a workaround now (assuming that the query is not
> too expensive). While ASCII cursors always hide the varchar sizes,
> binary ones return the size in actual data (by zero-padding the
> returned data to max size), so one can determine the actual max
> sizes by opening the query in binary cursor and then examining
> enough records to get one non-null field for each varchar field.
As of 6.3, this is only true of char() fields. Varchar() is now
variable length.
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: maillist@candle.pha.pa.us, hannu@trust.ee, byronn@insightdist.com, pgsql-hackers@postgreSQL.org
Subject: Re: [HACKERS] Re: [INTERFACES] retrieving varchar size
In-Reply-To: <199804231645.MAA26157@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox