Bug in "New entity classes from database"

[mvackel]

Hello,

when using the wizard "new entity classes from database" it seems that there is a bug when the Data Source has a broken view. Accessing the database directly, the view reports a problem as the referred database is no longer available. But the wizard is trying to get all the tables and views informations. When it gets to the bad view, the wizard freezes.

Sometimes I have to kill Netbeans. Sometimes it returnes to the wizard, but with no "Available Tables".

[Melongo Annabel]

Can you report this please at http://qa.netbeans.org under "Report A Problem"? Thanks.


From: mvackel <address-removed>
To: address-removed
Sent: Tuesday, August 25, 2009 4:00:55 PM
Subject: [nbj2ee] Bug in "New entity classes from database"

Hello,



when using the wizard "new entity classes from database" it seems that there is a bug when the Data Source has a broken view. Accessing the database directly, the view reports a problem as the referred database is no longer available. But the wizard is trying to get all the tables and views informations. When it gets to the bad view, the wizard freezes.



Sometimes I have to kill Netbeans. Sometimes it returnes to the wizard, but with no "Available Tables".

------------------------
Marcos Ackel

[Glenn Holmer]

On Tue, 2009-08-25 at 21:00 +0000, mvackel wrote:

[Jie Bie]

I'm having the same problem as the OP.

I'm using Netbeans 6.9.1 and attempting to use the "New Entity Class from Database" wizard to create a class to represent a table that exists on my SQL Server 2000 database.

Once I enter the appropriate connection string the wizard goes off and starts fetching the tables (as it should). When it has finished processing the tables it moves onto the views where it hits a problem. Netbeans simply freezes while the message "Retrieving the keys for view <view name>" is on the screen, with a frozen progress bar below.

I have found a roundabout way of fixing this, by copying the table I need into another schema and then using that schema in my connection string instead of the "dbo" one. However this isn't really a practical solution.

Does anyone have any idea whether or not this issue has been solved? I don't want to raise a bug report if there is an easy way round it.