On Tue, 2002-12-17 at 15:08, Anders Hermansen wrote:
> * Daniel Serodio (daniel@checkforte.com.br) wrote:
> > The Javadoc for DatabaseMetaData.getPrimaryKeys(...) clearly states that
> > catalog may be null, but doesn't mention anything about schema or table
> > being null. I understand this as meaning they (schema and table) can't
> > be null.
>
> Maybe you have an old javadoc? In my (1.4.1) it specifies that schema
> can be null as well. But it does not mention that table can be null. This is
> probably a bug in ojb then.
Old Javadoc indeed. I'm using 1.3.1. I can't recall right now, is the
JDBC in Java 1.3.1 is JDBC2? Maybe the app (reversedb) should try to
find out if it's talking to JDBC2 or JDBC3, then use table=null or not
accordingly. Is this viable?
> <quote>
> Parameters:
> catalog - a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without
acatalog; null means that the catalog name should not be used to narrow the search
> schema - a schema name; must match the schema name as it is stored in the database; "" retrieves those without a
schema;null means that the schema name should not be used to narrow the search
> table - a table name; must match the table name as it is stored in the database
> </quote>
>
>
> Anders
>
> --
> Anders Hermansen
> YoYo Mobile as
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
--
[]'s
Daniel Serodio