RE: RE: JDBC now needs updates for large objects

Prefixed with PM:

-- 
Peter Mount
Enterprise Support Officer, Maidstone Borough Council
Email: petermount@maidstone.gov.uk
WWW: http://www.maidstone.gov.uk
All views expressed within this email are not the views of Maidstone Borough
Council


-----Original Message-----
From: Dave Page [mailto:dpage@vale-housing.co.uk]
Sent: Tuesday, October 31, 2000 12:46 PM
To: 'Peter Mount'; 'pgsql-interfaces@postgresql.org'
Subject: RE: [INTERFACES] RE: JDBC now needs updates for large objects 




> -----Original Message-----
> From: Peter Mount [mailto:petermount@maidstone.gov.uk]
> Sent: 26 October 2000 08:32
> To: 'Dave Page'; 'pgsql-interfaces@postgresql.org'
> Subject: RE: [INTERFACES] RE: JDBC now needs updates for 
> large objects 
> 
> 
> Yes please. It would be a good place to start from existing views.
> 
> Peter
> 

Sorry for the delay Peter, I've been in other offices hanging around for BT
engineers!

PM: I know the feeling. Anyhow, I've had problems with the storms yesterday
morning (had no power first thing, couldn't get into work etc), so when the
power came back on, I finally started on them.

PM: Started on the query to get details on the columns, and I'm seeing some
wierd results. The original query retrieved the oid of the column type, and
jdbc then queried for the type name as a separate query (yes, I'm going to
try to amalgamate these). Anyhow, on different tables, and it appears to be
random, but if it occurs for a table, it always occurs) the first query
returns the type name not the oid. I'm going to try to get a fresh cvs out
due to the make problems I was having, just incase it's something unusual
with the working 7.1 backend I have.

There are various views below *which work for me*. They are designed to
allow pgAdmin users to generate reports of the objects in their databases.
Note that I've had to use functions quite a lot to avoid outer joins and
unions, and that the comments column(s) in each view are retrieved from
either pg_description or pgadmin_desc depending on whether the oid of the
object is above 18655 (the last possible non-system oid from my
experiments).

PM: Yes, I currently implement this by issuing a separate query on
pg_description. Once I get the  existing queries working I'm going to try to
use an outer join.

Regards,
Dave.