Mercurial > hg > monetdb-java

changeset 267:43ea6c50483e

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Correct return value for supportsIntegrityEnhancementFacility() Added explanation why we should return false.
author Martin van Dinther <martin.van.dinther@monetdbsolutions.com>
date Thu, 07 Mar 2019 17:46:34 +0100 (2019-03-07)
parents eefa7f625673
children ee4c826e3933
files src/main/java/nl/cwi/monetdb/jdbc/MonetDatabaseMetaData.java
diffstat 1 files changed, 10 insertions(+), 2 deletions(-) [+]
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
@@ -965,13 +965,21 @@ public class MonetDatabaseMetaData exten
 
 	/**
 	 * Is the SQL Integrity Enhancement Facility supported?
-	 * Our best guess is that this means support for constraints
+	 *
+	 * The SQL Integrity Enhancement facility offers additional tools for referential integrity,
+	 * CHECK constraint clauses, and DEFAULT clauses. Referential integrity allows specification of
+	 * primary and foreign keys with the requirement that no foreign key row may be inserted or
+	 * updated unless a matching primary key row exists. Check clauses allow specification of
+	 * inter-column constraints to be maintained by the database system.
+	 * Default clauses provide optional default values for missing data. 
+	 *
+	 * We currently do not supprt CHECK constraints (see bug 3568) nor deferrable FK constraints.
 	 *
 	 * @return true if so
 	 */
 	@Override
 	public boolean supportsIntegrityEnhancementFacility() {
-		return true;
+		return false;
 	}
 
 	/**