This is a good bug to fix... If you have the itch to address this yourself, I can provide pointers to fix the problem. Derby internally tries to recompile stored statements under some conditions, which probably shouldn't be attempted for readonly databases. I can provide more details if you or anyone else wants to work on this.
Satheesh Alex Miller wrote: >I think DERBY-854 (https://issues.apache.org/jira/browse/DERBY-854) is >critical for working with read-only databases in embedded mode. >Currently, the JDBC DatabaseMetaData methods are completely broken when >running in this mode. Thus, read-only databases cannot work with any >tool that imports metadata (which includes most JDBC tools I'm aware >of). > >Please vote for this bug if you would like to use read-only databases >from a zip file. My company would love to ship some example databases >in this way but have given up on Derby due to this bug. > >Alex Miller >Chief Architect >MetaMatrix > > > >-----Original Message----- >From: Rick Hillegas [mailto:[EMAIL PROTECTED] >Sent: Tuesday, February 14, 2006 12:13 PM >To: Derby Discussion; Derby Development >Subject: upcoming 10.2 release > >Dear Derby user community, > >Yesterday, the Derby developers started a discussion about the timing >and contents of the next (10.2) release. A feature freeze date of April >7 was suggested although we have not settled on this date yet. I would >estimate that the actual release would appear around two months after >feature freeze. > >Please let us know about any bugs which are particularly important to >you and which you would like to see fixed in this release. > >Thanks, >-Rick > > > > >
