db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eranda Sooriyabandara (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1958) improve XSDG3 error to print container, actual i/o operation, and file name.
Date Fri, 20 Aug 2010 14:22:17 GMT

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

Eranda Sooriyabandara updated DERBY-1958:
-----------------------------------------

    Attachment: Derby-1958.diff

Hi Bryan,
I came up with a patch. While creating this I faced a problem with the type variable in which
we define read/write. So I came up with a class variables for both type and file (openType
and fileName) where they are initialized at readPage/writePage methods. So what you think,
can we have such variable or does it need changes?

> improve XSDG3 error to print container, actual i/o operation, and file name.
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-1958
>                 URL: https://issues.apache.org/jira/browse/DERBY-1958
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.1.4
>            Reporter: Mike Matrigali
>            Assignee: Eranda Sooriyabandara
>            Priority: Trivial
>         Attachments: Derby-1958.diff, Derby-1958.diff, Derby-1958.diff, reproduce.diff
>
>
> The current error does not give enough information to know what container is the problem:
> ERROR XSDG3: Meta-data for Container
> org.apache.derby.impl.store.raw.data.RAFContainer@10632cd could not be
> accessed 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message