db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5886) FILE_CANNOT_REMOVE_FILE exception prints garbage.
Date Thu, 18 Apr 2013 18:14:13 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-5886:
----------------------------------

    Fix Version/s: 10.11.0.0

checked fix into trunk:
r1469505 | mikem | 2013-04-18 11:11:15 -0700 (Thu, 18 Apr 2013) | 8 lines

DERBY-5886 FILE_CANNOT_REMOVE_FILE exception prints garbage.

Added new messages to cover cases where no exception was available for
the second argument, and made text of those messages more specific to
the actual usage.  Fixed the calls in RAFContainer.java to be consistent, and
still use original error.
                
> FILE_CANNOT_REMOVE_FILE exception prints garbage.
> -------------------------------------------------
>
>                 Key: DERBY-5886
>                 URL: https://issues.apache.org/jira/browse/DERBY-5886
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.10.1.1
>            Reporter: Rick Hillegas
>            Assignee: Mike Matrigali
>              Labels: derby_triage10_10
>             Fix For: 10.11.0.0
>
>
> SQLState.FILE_CANNOT_REMOVE_FILE maps to a message which has 2 arguments. This SQLState
is used many times. It is variously given 1, 2, or 3 arguments. It's unclear whether we need
multiple messages here or whether a single message could be pressed into service for all cases.
As it is, some of these invocations are going to generate confusing garbage for the user.
This SQLState is used in the following classes:
> java/engine/org/apache/derby/impl/store/raw/data/EncryptData.java
> java/engine/org/apache/derby/impl/store/raw/data/RAFContainer.java
> java/engine/org/apache/derby/impl/store/raw/data/RFResource.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message