From f14b87203abd43215a45434c6c03dbaa582e8be3 Mon Sep 17 00:00:00 2001
From: moparisthebest <admin@moparisthebest.com>
Date: Fri, 2 Jun 2017 00:43:32 -0400
Subject: [PATCH] If we can not properly infer PreparedStatement bind in
 JdbcMapper, error out saying so

---
 .../com/moparisthebest/jdbc/codegen/JdbcMapperProcessor.java | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/jdbcmapper/src/main/java/com/moparisthebest/jdbc/codegen/JdbcMapperProcessor.java b/jdbcmapper/src/main/java/com/moparisthebest/jdbc/codegen/JdbcMapperProcessor.java
index 75bf63f..25581e0 100644
--- a/jdbcmapper/src/main/java/com/moparisthebest/jdbc/codegen/JdbcMapperProcessor.java
+++ b/jdbcmapper/src/main/java/com/moparisthebest/jdbc/codegen/JdbcMapperProcessor.java
@@ -514,8 +514,9 @@ public class JdbcMapperProcessor extends AbstractProcessor {
 			} else if (types.isAssignable(o, sqlArrayType)) {
 				method = "Array";
 			} else {
-				// probably won't get here ever, but just in case...
-				method = "Object";
+				// shouldn't get here ever, if we do the types should be more specific
+				processingEnv.getMessager().printMessage(Diagnostic.Kind.ERROR, "@JdbcMapper.SQL could not properly infer PreparedStatement bind call for param", param);
+				return;
 			}
 		w.write("ps.set");
 		w.write(method);