Re: DatabaseMetadata problems - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: DatabaseMetadata problems
Date
Msg-id 22680.999871116@sss.pgh.pa.us
Whole thread Raw
In response to Re: DatabaseMetadata problems  (Rene Pijlman <rene@lab.applinet.nl>)
Responses Re: DatabaseMetadata problems
List pgsql-jdbc
Rene Pijlman <rene@lab.applinet.nl> writes:
> Reading the book "Understanding the SQL standard" it seems that
> what the standard calls a schema is a database in PostgreSQL. A
> catalog is a set of schemas. Following the standard, a session
> is supposed to have access to a catalog, but in PostgreSQL it
> has access to a database.

> Perhaps this feature has not yet been implemented because of
> such fundamental mapping problems.

I think it'd be a mistake to expend much effort on this issue in JDBC
right now.  We will eventually implement SQL92-compliant schemas in the
backend, and once that happens it'll be possible to do something
reasonable with the catalog metadata routines in JDBC.  If you try
to make a half-usable implementation now, you'll just create backwards-
compatibility issues for the real implementation later.  So my counsel
is: acknowledge that it's broken, but ignore it for now.

When is "eventually"?  Possibly 7.3, but I can't promise anything...

            regards, tom lane

pgsql-jdbc by date:

Previous
From: "chris markiewicz"
Date:
Subject: Re: error - NOTICE: current transaction...MORE DETAIL...
Next
From: Bruce Momjian
Date:
Subject: Re: Read transactions don't work on 7.0.x db's 3rd attempt