RE: JDBC now needs updates for large objects

I was going to redo those queries this coming weekend anyhow (as thats when
I'll be getting some spare time next), as there are still some problems with
the existing ones.

Any other "minor" changes I should keep an eye out for?

Idea: As we have this type of query in more than one part of the source tree
(ie: psql, jdbc, probably odbc), should we have a section in the
documentation containing common queries, like: retrieving a list of tables,
views etc?

I haven't seen a definitive one in there, but it would be useful, and have
the other ones in the source be based on that one? Every time a change to
the system tables is made, unless everyone who maintains the code that's
dependent on it hears about it, the queries can quickly get out of sync.

Peter

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

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, October 24, 2000 2:58 AM
To: Peter Mount
Cc: pgsql-interfaces(at)postgreSQL(dot)org; pgsql-hackers(at)postgreSQL(dot)org
Subject: JDBC now needs updates for large objects

Peter,

As of current sources, large objects no longer occupy tables named
'xinvNNNN' nor indexes named 'xinxNNNN'. Therefore, it'd be appropriate
to remove the special tests that exclude tables/indices named that way
from the tests in DatabaseMetaData.java. I have not done this because
I'm not in a position to test changes to the JDBC driver; would you
please add it to your todo list?

regards, tom lane