[ http://issues.apache.org/jira/browse/DERBY-1072?page=comments#action_12370681 ]
Mayuresh Nirhali commented on DERBY-1072: ----------------------------------------- While a view is being Dropped, the TableDescriptor for the specified view is read. If this TableDescriptor is null then error X0X05 is thrown with message "Table <ViewName> does not exist.". This could be confusing to the user. The fix for this bug is to change the error message to "Table/View <viewname> does not exist", as suggested earlier. First, I would like to know if anyone has any other opinion reg. this fix ?? Please take a look at org/apache/derby/impl/sql/execute/DropViewConstantAction.executeConstantAction(Activation) for the case mentioned in the description. One more similar case is when, select query is fired on a view that does not exist. The error message in this case is, "Error 42X05: Table <viewname> does not exist". I am still looking for more cases, any more pointers are appreciated. Before, I start looking into how to modify message_XX.properties, I would like to know the safest way to find out the characters to be added for all the locales. One way of doing this to find out how '/view' is mapped in other locale properties file. I am wondering if there are any tools available with us for such conversion?? > Misleading/wrong error message while dropping a view > ---------------------------------------------------- > > Key: DERBY-1072 > URL: http://issues.apache.org/jira/browse/DERBY-1072 > Project: Derby > Type: Bug > Components: Newcomer, SQL > Versions: 10.1.2.2 > Environment: windows xp , jdk1.5 > Reporter: Manjula Kutty > Assignee: Mayuresh Nirhali > Priority: Minor > > while dropping a view which does not really exist on a database , the error > message thrown by ij says ERROR X0X05: Table 'VIEW222' does not exist. It > looks like we should make the error message to say that "Table/View" does > not exist, instead of "table". > Look at other messages that are shared for both Table and View. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
