[
https://issues.apache.org/jira/browse/DERBY-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165742#comment-13165742
]
Kathey Marsden commented on DERBY-4589:
---------------------------------------
I don't think it would be good to change the behavior which has always existed
which is that Derby will not attempt to create a database in a directory that
already exists. Also I think we never should delete user files on database
creation. The corruption might be something other than a failed create attempt.
I actually have seen user cases come in where someone had deleted the
service.properties file and we were able to recover their data by
reconstructing the file. If Derby had simply blown it away, such recovery would
not have been possible.
But yes, it looks like for DERBY-5526, the problem is the new error message
has been thrown where it shouldn't be, so fixing that should resolve the issue
for the user expecting the old error in that case.
> Corrupted database prevents startup and should be automatically repaired
> perhaps
> --------------------------------------------------------------------------------
>
> Key: DERBY-4589
> URL: https://issues.apache.org/jira/browse/DERBY-4589
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Affects Versions: 10.5.3.0
> Environment: Windows 2000, SP4. J2SE 1.6
> Reporter: Jeff Mckenzie
> Assignee: Rick Hillegas
> Fix For: 10.8.1.2, 10.9.0.0
>
> Attachments: 2010-03.zip, Test_4589.java, Test_4589.java,
> derby-4589-01-ab-missingServiceProperties.diff,
> derby-4589-01-ac-missingServiceProperties.diff
>
>
> I have found a database in my application that prevents startup due to it
> being corrupted.
> The driver reports that the database does not exist, even though it does.
> Then when my app tries to create the database using ;create=true; on the URL
> it fails.
> I think this happened due to the app being killed in Task Manager while it
> was creating the database.
> I have the database saved so that you can reproduce the problem. (I'm not
> sure if I can attach it yet)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
