[hibernate-issues] [Hibernate-JIRA] Closed: (HBX-830) Database errors should not be displayed in Log Error view
Max Rydahl Andersen (JIRA)
noreply at atlassian.com
Mon Dec 11 17:25:05 EST 2006
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-830?page=all ]
Max Rydahl Andersen closed HBX-830:
-----------------------------------
Fix Version: 3.2beta9
Resolution: Fixed
#1 is already done (afaik)
#3 is implemented now via HBX-837
for #2 I would rather find out why it concretly fails ? BIN$ table's should not be read, so not there fault..
> Database errors should not be displayed in Log Error view
> ---------------------------------------------------------
>
> Key: HBX-830
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-830
> Project: Hibernate Tools
> Type: Improvement
> Components: eclipse
> Versions: 3.2beta8
> Environment: Eclipse 3.2, Hibernate Tool 3.2 beta 8
> Reporter: Dariusz Tylus
> Fix For: 3.2beta9
>
>
> When user select Refresh in eg reveng editor and there is an error during reading database schema user is not notyiied about an error and see the incompleat database schema in the three.
> Such situation is common when you are using Oracle database and there is problem with BIN tables.
> Evry errors are logged to the PDE Runtime -> Log Error View. This view is for eclipse developers not for applications programers.
> Database problems are application specific so they should not be diplayed in Log Error view.
> My sugestion is:
> 1. Notify the user about dtdabase error when the database schema is read.
> 2. Mark the database tree in reveng editor as incompleate.
> 3. Stop logging database errors to the Log Error view
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list