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 124506 - Mismatch when using same database table name
Summary: Mismatch when using same database table name
Status: RESOLVED DUPLICATE of bug 89092
Alias: None
Product: db
Classification: Unclassified
Component: DB schema (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P1 blocker (vote)
Assignee: David Vancouvering
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-29 09:21 UTC by ads59
Modified: 2008-01-11 23:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ads59 2007-12-29 09:21:37 UTC
Hi,
My issue is about two database tables having same name (in different
databases) and each one bound to a swing "table" component. The two
swing tables are displaying same data while they are not bound to same
database tables.

I have created two postgreSQL databases having same properties, both having a table
called tb_test. The database schema looks like :

db_test.tb_test( id : biginteger, name : varchar )
db_test2.tb_test( id2 : biginteger, name2 : varchar )

I created 2 database connections in the "services" browser.

I put two swing "table" components on a form, then I Drag&Drop the first db_test.tb_test
to the first component and then I D&D the second db_test2.tb_test to the second component.
==> They are displaying same database table content.

It seems that netbeans 6.0 can't differentiate same table names coming from different databases.

Antonio.
Comment 1 David Vancouvering 2008-01-07 23:33:10 UTC
Apologies for not responding sooner, I have been on vacation.

Are these two databases on the same PostgreSQL connection, or are they on different connections?  If they are on the
same connection, then it sounds like they are different *schemas*, not different databases.  I just want to get clear on
this, because I know that the swing table component binding stuff has a bug where it does not include a schema name when
specifying a table, and this has caused other problems.
Comment 2 David Vancouvering 2008-01-07 23:54:22 UTC
Need more data before I can evaluate.
Comment 3 David Vancouvering 2008-01-10 21:46:48 UTC
ads59: are you there? It would be good to track this down if you can provide some more information.
Comment 4 David Vancouvering 2008-01-11 23:05:32 UTC
Since I'm not getting more information, I'm going to have to assume that this is caused by the fact that the generated
code for the database desktop application does not include the schema name, and am closing this as a duplicate.  ads59,
if you have more information to provide that might show this to be otherwise, please let us know.

*** This issue has been marked as a duplicate of 89092 ***