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] [Assigned] (DERBY-5886) FILE_CANNOT_REMOVE_FILE exception prints garbage.
Date Tue, 16 Apr 2013 19:17:16 GMT

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

Mike Matrigali reassigned DERBY-5886:

    Assignee: Mike Matrigali
> 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:
>            Reporter: Rick Hillegas
>            Assignee: Mike Matrigali
>              Labels: derby_triage10_10
> 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

View raw message