Mercurial > hg > monetdb-java
view ChangeLog @ 423:de2ef68b672f mapihandshake
Allow to set fetchsize from the connection url
author | Joeri van Ruth <joeri.van.ruth@monetdbsolutions.com> |
---|---|
date | Tue, 02 Feb 2021 14:21:22 +0100 (2021-02-02) |
parents | 163b784aa93b |
children | e79bfbd0553e |
line wrap: on
line source
# ChangeLog file for monetdb-java # This file is updated with Maddlog * Thu Jan 28 2021 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Corrected the ordering of the output of DatabaseMetaData methods getImportedKeys(), getExportedKeys() and getCrossReference(). In cases where a table would have multiple fks to the same external table, the output was not as expected. This has been corrected, so the columns now appear in the order as defined in the creation of the fks. * Thu Jan 28 2021 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - The dumping of table definitions from JdbcClient program has been improved. It now includes the ON UPDATE and ON DELETE rules for foreign key constraints. Also it no longer generates CREATE INDEX statements for foreign key constraints whose name is not system generated but user specified. * Thu Jan 14 2021 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Improved DatabaseMetaData.getTypeInfo() output for temporal data types: sec_interval, day_interval, month_interval, date, time, timetz, timestamp and timestamptz. * Wed Jan 6 2021 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Corrected output of resultset columns UPDATE_RULE and DELETE_RULE when calling DatabaseMetaData API methods getImportedKeys() or getExportedKeys() or getCrossReference(). These columns used to always return DatabaseMetaData.importedKeyNoAction but now they can also report the other values when set: DatabaseMetaData.importedKeyCascade or DatabaseMetaData.importedKeyRestrict or DatabaseMetaData.importedKeySetNull or DatabaseMetaData.importedKeySetDefault. * Thu Nov 12 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Moved Java classes from packages starting with nl.cwi.monetdb.* to package org.monetdb.* This naming complies to the Java Package Naming convention as MonetDB's main website is www.monetdb.org. To prevent problems with existing Java programs and JDBC driver configurations we still support usage of the following classes: nl.cwi.monetdb.jdbc.MonetDriver nl.cwi.monetdb.jdbc.types.INET nl.cwi.monetdb.jdbc.types.URL nl.cwi.monetdb.mcl.net.MapiSocket nl.cwi.monetdb.client.JdbcClient They are implemented as simple wrappers of their org.monetdb.* equivalents. Note: These nl.cwi.monetdb.* classes are now marked as deprecated and may be removed in a future release. If you still use them in your Java code or configuration files, update them to use the new package names. * Thu Oct 29 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Extended JdbcClient program with 3 new commands to quickly validate data integrity: \vsci validate sql system catalog integrity \vsi <schema> validate integrity of data in the given schema \vdbi validate integrity of data in all user schemas in the database The current validations include: - Primary Key uniqueness - Primary Key column(s) being NOT NULL (currently only for \vsci) - Unique constraint uniqueness - Foreign Key referential integrity - Column NOT NULL constraint - Varchar(n) max length constraint - Idem for char(n), clob(n), blob(n), json(n) and url(n). It can be usefull to run \vsci before and after an upgrade of MonetDB server. Use \vsi my_schema to validate data in all tables of a specific schema. Use \vdbi to validate integrity of data in all user schemas in the database. Note: this can take a while, depending on your number of user schemas, tables and tables sizes. Despite being tested on several internal dbs the functionality is still beta, so you can get false errors reported. If you encounter these let us know asap. * Thu Oct 8 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Improved performance of ResultSetMetaData methods isAutoIncrement(), getPrecision() and getScale() significantly for columns of specific data types as in some cases no costly meta data query is executed anymore. * Thu Oct 8 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - The connection properties treat_clob_as_varchar and treat_blob_as_binary are now set to true by default within the JDBC driver. This is done as it results by default in less memory usage, (much) faster response and better user experience for many generic JDBC applications (like SQuirreL SQL, DBeaver, etc) when fetching data from CLOB or BLOB result columns. See release.txt for more information and how you can turn it off to get the old JDBC driver behavior if you require it. * Wed Oct 7 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Added support for new Java 8 java.sql.Types: Types.TIME_WITH_TIMEZONE and Types.TIMESTAMP_WITH_TIMEZONE. * Wed Sep 23 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Updated JDBC driver to comply with JDBC 4.2 interface now we compile for Java 8. This includes: - adding 8 methods to MonetCallableStatement - adding 2 methods to MonetDatabaseMetaData - adding 3 methods to MonetPreparedStatement - adding 4 methods to MonetResultSet - adding 8 methods to MonetStatement * Wed Sep 23 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Corrected MonetDatabaseMetaData.getTypeInfo() - The LITERAL_PREFIX column now includes the required casting name for types: clob, inet, json, url, uuid and blob. - The SEARCHABLE column now returns typePredBasic instead of typeSearchable for type: blob. - The AUTO_INCREMENT column now returns false for types: hugeint, decimal, oid and wrd. * Thu Sep 10 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Removed support for deprecated MD5 encryption algorithm in MapiSocket. * Wed Sep 9 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Corrected Statement.executeBatch() method. It now implicitly clears the batch buffer, ready to accept new addBatch() calls without the need for an explicit clearBatch() call. See also https://www.monetdb.org/bugzilla/show_bug.cgi?id=6953 * Wed Feb 19 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - Corrected the return value of getCatalogTerm() to "cat". * Wed Feb 12 2020 Martin van Dinther <martin.van.dinther@monetdbsolutions.com> - As Java 7 is no longer supported we now compile for Java 8 as the minimum required JVM version (profile compact2).