db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5232) Put a stern README file in log and seg0 directories to warn users of corrpution they will cause if they touch files there
Date Thu, 15 Nov 2012 16:32:12 GMT

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

Kim Haase updated DERBY-5232:

    Attachment: DERBY-5232-kim.diff

Happy to help with this. I agree completely with Kathey's suggestion about the file names
-- the separate words are indeed preferable to the contraction.

I am attaching a suggested patch for messages.xml, DERBY-5232-kim.diff, with some wording
fixes. (I hope it merges all right with Mamta's latest.) I do have a couple of questions --

For consistency, I used the term NON-RECOVERABLE, since that's what we use in our SQLSTate
error messages. However, the Oracle terminology guide for my organization says to use NONRECOVERABLE
(no hyphen), while the official Oracle style guide says to use IRRECOVERABLE or NOT RECOVERABLE.
What does the IBM style guide say? Or should we just worry about consistency with the error

I notice a comment saying, "Translators: Please translate the ALL CAPS words." However, there's
a mixed case sentence at the top of each saying, "Do not touch files in this directory!" I
assume we want this to be translated too -- is it understood that they always translate mixed-case
text but not all-caps text? Sorry to be ignorant about our localization practices.

> Put a stern README file in log and seg0 directories to warn users of corrpution they
will cause if they touch files there
> -------------------------------------------------------------------------------------------------------------------------
>                 Key: DERBY-5232
>                 URL: https://issues.apache.org/jira/browse/DERBY-5232
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>             Fix For:
>         Attachments: DERBY-5232-kim.diff, DERBY5232_patch1_diff.txt, DERBY5232_patch1_stat.txt,
DERBY5232_patch2_diff.txt, DERBY5232_patch2_stat.txt, DERBY5232_patch3_diff.txt, DERBY5232_patch3_stat.txt,
DERBY5232_patch4_diff.txt, DERBY5232_patch4_stat.txt, DERBY5232_patch5_diff.txt, DERBY5232_patch5_stat.txt,
DERBY5232_patch6_diff.txt, DERBY5232_patch6_stat.txt, DERBY5232_patch7_diff.txt, DERBY5232_patch7_stat.txt,
DERBY5232_test_patch1_diff.txt, DERBY5232_test_patch1_stat.txt, DERBY5232_test_patch2_diff.txt,
> Users often on bad advice or desperation  touch or delete files in the log or seg0 directories
(mostly log).
> I think it would be good for new databases and on upgrade that a file be created in these
directories with a name like:
> or some such to warn of the perils of doing this and the corrupting effects and how it
can eliminate any possibility of salvage. It should also encourage users to make a zip backup
of the database directory with no jvm currently accessing it before trying to do anything
with the database if it appears to be already corrupt.  Also point to backup/restore documentation
and encourage restore of a good backup into an empty directory if the database is corrupt.
> I'm not sure if it would help but it couldn't hurt.

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