From: | Anders Hermansen <anders(at)yoyo(dot)no> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [PATCH] NPE in meta data getPrimaryKeys() |
Date: | 2002-12-17 17:08:14 |
Message-ID: | 20021217170814.GA18398@online.no |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
* Daniel Serodio (daniel(at)checkforte(dot)com(dot)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.
<quote>
Parameters:
catalog - a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog; 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
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Serodio | 2002-12-17 17:21:03 | Re: [PATCH] NPE in meta data getPrimaryKeys() |
Previous Message | Anders Hermansen | 2002-12-17 16:59:39 | Re: [PATCH] NPE in meta data getPrimaryKeys() |