On May 21, 5:14 pm, Saverio Miroddi <[EMAIL PROTECTED]> wrote:
> You forgot to add this regression ;-)
>
> 418861 [Thread-4] ERROR
> net.sourceforge.squirrel_sql.client.session.SQLExecuterTask - Can't
> Set MaxRows
> java.sql.SQLException: statement is not executing
> at org.sqlite.Stmt.checkOpen(Stmt.java:41)
> at org.sqlite.Stmt.setMaxRows(Stmt.java:199)
> at
> net.sourceforge.squirrel_sql.client.session.SQLExecuterTask.run(SQLExecuterTask.java:
> 158)
> at
> net.sourceforge.squirrel_sql.fw.util.TaskExecuter.run(TaskExecuter.java:
> 82)
> at java.lang.Thread.run(Unknown Source)
>
> which happens when I use the pure Java driver with SquirrelSQL.
I see the same thing with nested-vm 48. Surely, it is valid to call
setMaxRows prior to executing the statement?
At least, many other drivers we've worked with allow this.
Stmt.checkOpen seems to want pointer to be set; it is
not set until the statement is executed. Perhaps Stmt could maintain
it's own instance variable called maxRows and
use it to set the ResultSet's max rows?
Rob
--~--~---------~--~----~------------~-------~--~----~
Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en
To unsubscribe, send email to [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
