Driver Bug
От | John LH |
---|---|
Тема | Driver Bug |
Дата | |
Msg-id | e91948a90612201022w20864c67keca55ec2ae113d2@mail.gmail.com обсуждение исходный текст |
Ответы |
Re: Driver Bug
|
Список | pgsql-jdbc |
Hi,
I've found a bug in the drivers which seem to occur in the "8.1-408 JDBC 3" and "8.2-504 JDBC 3" drivers when executing on a 8.1 and 8.2 PG Server. The problem does not occur on a 8.0 server.
The problem occurs when the following situation is produced ...
1. Connection.autoCommit(true);
2. Statement.setMaxRows(1);
3. Statement.execute("select * from information_schema.parameters");
In this case, the Statement.execute() will never return and basically put the application in a hanging state. If the Connection.autoCommit() is set to false then all works well. If the Statement.setMaxRows() is set to a number higher then the number of rows to be returned then all works well. But if you auto commit is true and max rows is less then the total number of rows and the statement is executed on PG 8.1 or 8.2.
Any ideas?
thanks
-John
I've found a bug in the drivers which seem to occur in the "8.1-408 JDBC 3" and "8.2-504 JDBC 3" drivers when executing on a 8.1 and 8.2 PG Server. The problem does not occur on a 8.0 server.
The problem occurs when the following situation is produced ...
1. Connection.autoCommit(true);
2. Statement.setMaxRows(1);
3. Statement.execute("select * from information_schema.parameters");
In this case, the Statement.execute() will never return and basically put the application in a hanging state. If the Connection.autoCommit() is set to false then all works well. If the Statement.setMaxRows() is set to a number higher then the number of rows to be returned then all works well. But if you auto commit is true and max rows is less then the total number of rows and the statement is executed on PG 8.1 or 8.2.
Any ideas?
thanks
-John
В списке pgsql-jdbc по дате отправления: