Re: Roadmap for FE/BE protocol redesign - Mailing list pgsql-hackers

From Dave Page
Subject Re: Roadmap for FE/BE protocol redesign
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B8259D8D@mail.vale-housing.co.uk
Whole thread Raw
In response to Roadmap for FE/BE protocol redesign  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Roadmap for FE/BE protocol redesign  (Dave Cramer <dave@fastcrypt.com>)
Re: Roadmap for FE/BE protocol redesign  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

> -----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.

pgsql-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Roadmap for FE/BE protocol redesign
Next
From: "Dave Page"
Date:
Subject: Re: Roadmap for FE/BE protocol redesign