[sqlite] 3.8.7 work-around for handling datetime values since it reports DATE type

... also no need to case-convert identifiers since SQLite's meta-data returns false

Author: kares

src/java/arjdbc/sqlite3/SQLite3RubyJdbcConnection.java

@@ -37,6 +37,7 @@
 import java.sql.Statement;
 import java.sql.DatabaseMetaData;
 import java.sql.Savepoint;
+import java.sql.Types;
 import java.util.ArrayList;
 import java.util.List;
 
@@ -217,14 +218,10 @@ else if ( nameParts.length == 3 ) {
             name = nameParts[2];
         }
 
-        name = caseConvertIdentifierForJdbc(connection, name);
-
         if ( schema != null ) {
-            schema = caseConvertIdentifierForJdbc(connection, schema);
             // NOTE: hack to work-around SQLite JDBC ignoring schema :
             return new TableName(catalog, null, schema + '.' + name);
         }
-
         return new TableName(catalog, schema, name);
     }
 
@@ -239,6 +236,13 @@ protected IRubyObject jdbcToRuby(final ThreadContext context,
         if ( resultSet instanceof ResultSetMetaData ) {
             type = ((ResultSetMetaData) resultSet).getColumnType(column);
         }
+        // since JDBC 3.8 there seems to be more cleverness built-in that
+        // seems (<= 3.8.7) to get things wrong ... reports DATE SQL type
+        // for "datetime" columns :
+        if ( type == Types.DATE ) {
+            // return timestampToRuby(context, runtime, resultSet, column);
+            return stringToRuby(context, runtime, resultSet, column);
+        }
         return super.jdbcToRuby(context, runtime, column, type, resultSet);
     }