This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 154643 - Metadata API: Java DB default catalog has null name
Summary: Metadata API: Java DB default catalog has null name
Status: RESOLVED WONTFIX
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Vancouvering
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-04 18:34 UTC by David Vancouvering
Modified: 2009-02-19 20:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Vancouvering 2008-12-04 18:34:47 UTC 
When you get the default catalog for Java DB, it's always null
Comment 1 David Vancouvering 2008-12-05 00:27:44 UTC 
It's actually valid to have a null catalog name for the default catalog.  It's better than having *no* default catalog,
 which would cause all sorts of problems.  Here's the response from Lance on the derby-user list:

=====

Depends on the concept in Derby of what a catalog is as your mileage can vary between databases.
Some vendors treat it as the database name, others do not.

Null is allowed to be returned if the concept of catalog is not applicable to a given database

Regards
Lance


David Van Couvering wrote:

    Shouldn't Connection.getCatalog() return the name of the database you are connected to, and shouldn't
DMD.getCatalogs() return a result set with one row, representing the database you're connected to?

    This is causing us a bit of a headache when we're trying to inspect a Derby database in NetBeans...

    Thanks,

    David
Comment 2 David Vancouvering 2008-12-05 00:28:12 UTC 
See previous comment...