diff release.txt @ 710:437e51b4c169

Future versions of MonetDB (post Sep2022) will have capability to parse and execute ODBC/JDBC escape sequence syntax. Reflect this behavior in Statement.setEscapeProcessing(boolean enable).
author Martin van Dinther <martin.van.dinther@monetdbsolutions.com>
date Thu, 22 Dec 2022 14:53:54 +0100 (2022-12-22)
parents ee1f3b3ff5fd
children 7cec464246f2
line wrap: on
line diff
--- a/release.txt
+++ b/release.txt
@@ -116,15 +116,20 @@ Currently implemented JDBC 4.2 interface
     - executeUpdate with column indices or names
     - setMaxFieldSize
     - setCursorName
-    - setEscapeProcessing on
+    - setEscapeProcessing on for Sep2022 (11.45) or older servers
+    - setEscapeProcessing off for Sep2022 (11.45) or older servers
 
   * java.sql.PreparedStatement
     The next methods are NOT useable/supported:
     - setArray
-    - setAsciiStream, setBinaryStream, setUnicodeStream
+    - setAsciiStream
+    - setBinaryStream
     - setBlob
     - setNClob
-    - setRef, setRowId, setSQLXML
+    - setRef
+    - setRowId
+    - setSQLXML
+    - setUnicodeStream (note: this method is Deprecated)
 
   * java.sql.ParameterMetaData
 
@@ -136,6 +141,15 @@ Currently implemented JDBC 4.2 interface
       because output parameters in stored procedures are not supported by MonetDB
     - wasNull() method because output parameters in stored procedures are
       not supported by MonetDB
+    - setArray
+    - setAsciiStream
+    - setBinaryStream
+    - setBlob
+    - setNClob
+    - setRef
+    - setRowId
+    - setSQLXML
+    - setUnicodeStream (note: this method is Deprecated)
 
   * java.sql.ResultSet
     The next methods are NOT useable/supported: