From: Hiroshi Inoue <inoue@tpf.co.jp>
To: 'Zeugswetter Andreas SB SD' <ZeugswetterA@spardat.at>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: 'Bruce Momjian' <pgman@candle.pha.pa.us>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Wed, 12 Mar 2003 23:32:45 +0900
Message-ID: <000901c2e8a4$40b883f0$0e283ddb@PbgX> (raw)
In-Reply-To: <46C15C39FEB2C44BA555E356FBCD6FA4961F5A@m0114.s-mxs.net>
> -----Original Message-----
> From: Zeugswetter Andreas SB SD [mailto:ZeugswetterA@spardat.at]
>
> Hiroshi Inoue wrote:
> > Tom Lane wrote:
> > >
> > > Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > > > What the driver has suffered from is to get the
> > > > fields' info of a query result or the parameters'
> > > > info of a statement. The info is needed even before
> > > > the execution of the statement(i.e it's only prepared).
> > >
> > > Hm. Are you saying that you would like PREPARE to send back a
> > > RowDescription ('T') message?
> >
> > I'm not sure if PREPARE should return the info directly.
> > Maybe it should be returned only when it is requested.
> >
> > > Or is there more to it than that?
> >
> > More detailed field info is needed anyway.
> > For example the RowDescription contains neither
> > the base column name, the table name nor the
> > schema name currently and so the current odbc
> > driver couldn't return the info correctly.
>
> But it only needs that info to do system catalog lookups for
> type, length etc.
> Imho the target should be to not need catalog lookups, but
> get all needed info
> from the 'T' message, no?
Maybe.
>
> > The ODBC function SQLDescribeCol or SQLColAttribute
> > requires various kind of fields' info.
>
> RETCODE SQL_API SQLDescribeCol(
> HSTMT hstmt,
> UWORD icol,
> UCHAR FAR *szColName,
> SWORD cbColNameMax,
> SWORD FAR *pcbColName,
> SWORD FAR *pfSqlType,
> UDWORD FAR *pcbColDef,
> SWORD FAR *pibScale,
> SWORD FAR *pfNullable);
>
> So you see it does not need tablename or schema.
Oh yes but SQLColAtrribute should return
such info if requested.
regards,
Hiroshi Inoue
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: inoue@tpf.co.jp, ZeugswetterA@spardat.at, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
In-Reply-To: <000901c2e8a4$40b883f0$0e283ddb@PbgX>
* 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