Re: Roadmap for FE/BE protocol redesign

This may be problematic in the future if we change attrelid, attnum.

My preference would be to be able to query the backend for the
information if I need it. It is rarely required.

ie give me the meta data for the last resultset.

Dave

On Wed, 2003-03-12 at 09:49, Dave Page wrote:
> > -----Original Message-----
> > From: Zeugswetter Andreas SB SD [mailto:ZeugswetterA@spardat.at] 
> > Sent: 12 March 2003 09:50
> > To: Hiroshi Inoue; Tom Lane
> > Cc: Bruce Momjian; pgsql-hackers@postgresql.org; 
> > pgsql-interfaces@postgresql.org
> > Subject: Re: [HACKERS] Roadmap for FE/BE protocol redesign
> > 
> > > 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.
> 
> No, but with them we can avoid cluttering the wire protocol with fields
> for all this, and the JDBC required data. With 2 numeric columns
> (attrelid, attnum), any application/interface can query the system
> catalogs easily for whatever extra info they like.
> 
> Regards, Dave.
-- 
Dave Cramer <Dave@micro-automation.net>
-- 
Dave Cramer <dave@fastcrypt.com>
Cramer Consulting