Hi Alex, What is the resultSetConcurrency type that you are using while creating the SELECT statement ?
I have not been able to reproduce this issue on a read-only db with Derby 10.2.2.0 - (485682) and using different result set types and concurrency. Moreover I don't think the error could be because of the resultSetType - ( ResultSet.TYPE_FORWARD_ONLY, ResultSet.TYPE_SCROLL_INSENSITIVE, or ResultSet.TYPE_SCROLL_SENSITIVE ) Using ResultSet.CONCUR_UPDATABLE type of resultSetConcurrency the select does fail while opening the result set (first iteration) with 'ERROR 40XD1: Container was opened in read-only mode.' as Suresh pointed out. In any case, if you are able to provide a reproducible test that will be really useful. -Rajesh On 2/2/07, Alex Pooley <[EMAIL PROTECTED]> wrote:
I'm iterating a ResultSet from a read-only database. If the ResultSet is not created from a TYPE_FORWARD_ONLY Statement, then on interation 230 the following exception is thrown: "java.sql.SQLException: Container was opened in read-only mode." I have set derby.storage.tempDirectory, and derby.stream.error.file to writable locations as the docs specify. Is this behavior correct? Thanks, Alex.
