[
https://issues.apache.org/jira/browse/DERBY-4589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849258#action_12849258
]
Rick Hillegas commented on DERBY-4589:
--------------------------------------
Other people have been confused by this behavior it seems.
Various tasks have to be performed before the database exists. For instance,
service.properties must be written and the system tables must be created. What
should happen if you try to connect to a partially created database?
1) Should you get a message saying that the database is unusable rather than a
message saying that the database does not exist?
2) Should Derby raise an error saying that it is deleting or renaming the
half-created database so that you can retry database creation?
Thanks.
> 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
> Affects Versions: 10.5.3.0
> Environment: Windows 2000, SP4. J2SE 1.6
> Reporter: Jeff Mckenzie
> Attachments: 2010-03.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
