You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by Øystein Grøvlen <Oy...@Sun.COM> on 2005/10/03 16:02:49 UTC

Re: [jira] Commented: (DERBY-555) Unable to restart after disk is full

>>>>> "MM" == Mike Matrigali <mi...@sbcglobal.net> writes:

    MM> I like the idea of building the message into the normal boot rather than
    MM> generating an error for every db in a jar access - what do others think?

Mike,

Pardon my ignorance, but I am not quite sure what you mean by
"generating an error for every db in a jar access".

-- 
Øystein

Re: [jira] Commented: (DERBY-555) Unable to restart after disk is full

Posted by Mike Matrigali <mi...@sbcglobal.net>.

What I was referring to is that Derby can be configured to access a 
database which is stored totally in a jar file in the classpath.  In
that case the datbase is always read only, and it is not an error that
it is read only.

Øystein Grøvlen wrote:
>>>>>>"MM" == Mike Matrigali <mi...@sbcglobal.net> writes:
> 
> 
>     MM> I like the idea of building the message into the normal boot rather than
>     MM> generating an error for every db in a jar access - what do others think?
> 
> Mike,
> 
> Pardon my ignorance, but I am not quite sure what you mean by
> "generating an error for every db in a jar access".
>