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 <[EMAIL PROTECTED]> 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".
