[
https://issues.apache.org/jira/browse/DERBY-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165600#comment-13165600
]
Kathey Marsden commented on DERBY-4589:
---------------------------------------
The SQState change on the error on database creation if a database exists at a
minimum needs a release note, but I started a conversation about why it was
changed in DERBY-5526
https://issues.apache.org/jira/browse/DERBY-5526?focusedCommentId=13165598&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13165598
> 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
