diff src/main/java/nl/cwi/monetdb/jdbc/MonetDatabaseMetaData.java @ 53:6cc63d6cb224

Implemented fix as suggested in Bug 3973 The MapiSocket object now supports getting and setting the socket timeout, even before the TCP socket is created. Also improved the close() method to continue closing all opened resources, even if one of them failed to close. To set the socket timeout specify it in the JDBC URL, for example: jdbc:monetdb://localhost:50000/demo?so_timeout=8000 This enables the timeout and sets it to 8000 milliseconds (= 8 seconds). By default the timeout is not set, so wait infinitely.
author Martin van Dinther <martin.van.dinther@monetdbsolutions.com>
date Thu, 17 Nov 2016 17:42:41 +0100 (2016-11-17)
parents 5d4524c27902
children e605cdd6373f b9b35ca2eec2
line wrap: on
line diff
--- a/src/main/java/nl/cwi/monetdb/jdbc/MonetDatabaseMetaData.java
+++ b/src/main/java/nl/cwi/monetdb/jdbc/MonetDatabaseMetaData.java
@@ -3809,7 +3809,7 @@ public class MonetDatabaseMetaData exten
 		"SELECT 'debug', 5, 'false', 'boolean flag true or false' UNION ALL " +
 		"SELECT 'hash', 128, '', 'hash string' UNION ALL " +
 		"SELECT 'treat_blob_as_binary', 5, 'false', 'boolean flag true or false' UNION ALL " +
-		"SELECT 'so_timeout', 10, '0', 'timeout of communication socket. 0 means no timeout is set' " +
+		"SELECT 'so_timeout', 10, '0', 'timeout (in milliseconds) of communication socket. 0 means no timeout is set' " +
 		"ORDER BY \"NAME\"";
 
 		return executeMetaDataQuery(query);