> -----Original Message-----
> From: Peter Eisentraut [mailto:peter_e@gmx.net]
> Sent: 12 March 2003 17:46
> To: Dave Page
> Cc: Tom Lane; PostgreSQL Development
> Subject: RE: [HACKERS] Roadmap for FE/BE protocol redesign
>
>
> What you need is an updateable cursor on the server side. It
> has all the facilities you need, including standardized ways
> to find out the updatability metadata. Please concentrate on
> that and do not attempt to clutter the wire protocol with
> data that will not withstand a throrough investigation of semantics.
That may be true for pgAdmin III, (though it probably won't help through
an ODBC/ADO interface as pgAdmin II uses), but it doesn't help ODBC,
JDBC, dotNET DP etc. provide the metadata on resultsets that their specs
require them to.
What prompted me to think about this issue (again), is that the ODBC
driver incorrectly reports columns in a resultset as nullable, because
it has no way of telling otherwise. This issue breaks OpenOffice which
is using perfectly valid apis. pgAdmin III just happens to be able to
benefit from such an update as well.
Regards, Dave.