[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12357725 ]
Satheesh Bandaram commented on DERBY-506:
-
Thanks Oyvind for removing QueryTimerTask.java. Thanks Army and Oyvind for
pointing out that unrecognized SET statements
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12357597 ]
Oyvind Bakksjo commented on DERBY-506:
--
Sendingjava/client/org/apache/derby/client/am/PreparedStatement.java
Sending
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12357610 ]
Satheesh Bandaram commented on DERBY-506:
-
Thanks for the useful and good patch!! I did a quick review of the code and
have couple of comments:
1) Is there any
Satheesh Bandaram (JIRA) wrote:
2) What would happen if a 10.2 client tries to send a SET STATEMENT_TIMEOUT
statement to a 10.1 server? There doesn't seem to be any mechanism to prevent
unpleasant events.
I was reviewing the patch and decided to look into your question more, and I
think
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331714 ]
Oyvind Bakksjo commented on DERBY-506:
--
Sending the EXCSQLSET when the JDBC call [to Statement.setQueryTimeout()] is
made would cause an additional round-trip between the
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331730 ]
Kathey Marsden commented on DERBY-506:
--
My experience with client side code that has tried to do this in past is that
it has historically caused trouble.Common
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331738 ]
Oyvind Bakksjo commented on DERBY-506:
--
I understand your points, but with regards to setQueryTimeout(), I honestly
think you're making too much of this. ;-) To make my
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331742 ]
Kathey Marsden commented on DERBY-506:
--
I see your point about it being similar to the other attributes. Your
approach sounds ok to me then, especially since there
[
http://issues.apache.org/jira/browse/DERBY-506?page=comments#action_12331512 ]
Kathey Marsden commented on DERBY-506:
--
I think the EXCSQLSET is a good way to go but would prefer to see it made as a
call with setQueryTimeout when the JDBC call is
