Subject | Re: rs.getStatement |
---|---|
Author | Roman Rokytskyy |
Post date | 2002-09-17T16:16:26Z |
Hi,
object is closed, its current ResultSet object, if one exists, is also
closed.". So, I think, our driver works correctly.
Usually your code should look like this:
rs.close();
stmt.close();
possible, try to get our driver source code and comment the line that
throws an exception if you try to close result set that is already
closed. However, I do not think that we will fix this in CVS.
Best regards,
Roman Rokytskyy
> rs.getStatement.close();Javadoc for the java.sql.Statement.close() says "When a Statement
> rs.close();
>
> The rs.getStatment.close() line always errors saying the statement
> is already closed. How do I know its already closed?
object is closed, its current ResultSet object, if one exists, is also
closed.". So, I think, our driver works correctly.
Usually your code should look like this:
rs.close();
stmt.close();
> Is it to do with automatic transactions?No.
> Are there any workarounds?Not really... I would suggest to change your code. If this is not
possible, try to get our driver source code and comment the line that
throws an exception if you try to close result set that is already
closed. However, I do not think that we will fix this in CVS.
> By the way the line was added to prevent a memory leak in the systemWas that our driver?
> when the same transaction was being used over and over again.
Best regards,
Roman Rokytskyy