From 9305e305d34515deb9c336f6808db65a19e307df Mon Sep 17 00:00:00 2001 From: Lukas Eder Date: Wed, 22 Jan 2014 11:11:52 +0100 Subject: [PATCH] [#2963] Lower log level for warnings about unknown SQL data types from MetaDataFieldProvider (plain SQL) --- .../main/java/org/jooq/impl/MetaDataFieldProvider.java | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/jOOQ/src/main/java/org/jooq/impl/MetaDataFieldProvider.java b/jOOQ/src/main/java/org/jooq/impl/MetaDataFieldProvider.java index 3abb756962..b136ba6604 100644 --- a/jOOQ/src/main/java/org/jooq/impl/MetaDataFieldProvider.java +++ b/jOOQ/src/main/java/org/jooq/impl/MetaDataFieldProvider.java @@ -94,7 +94,7 @@ class MetaDataFieldProvider implements Serializable { // This happens in Oracle for empty cursors returned from stored // procedures / functions catch (SQLException e) { - log.warn("Cannot fetch column count for cursor : " + e.getMessage()); + log.info("Cannot fetch column count for cursor : " + e.getMessage()); fieldList.add(field("dummy")); } @@ -122,10 +122,11 @@ class MetaDataFieldProvider implements Serializable { } } - // [#650, #667] TODO This should not happen. All types - // should be known at this point + // [#650, #667] All types should be known at this point, but in plain + // SQL environments, it is possible that user-defined types, or vendor-specific + // types (e.g. such as PostgreSQL's json type) will cause this exception. catch (SQLDialectNotSupportedException ignore) { - log.warn("Not supported by dialect", ignore.getMessage()); + log.debug("Not supported by dialect", ignore.getMessage()); } fieldList.add(field(name, dataType));