Since ER4 there are new columns returned by ModeShape JDBC driver jcr:path, jcr:name, jcr:score, mode:localName, mode:depth.

When ModeShape.vdb is used then mode_depth is of type long and jcr_score of type double.
10:01:25,904 INFO [STDOUT] jcr_name = of type java.lang.String, 12
10:01:25,904 INFO [STDOUT] jcr_path = / of type java.lang.String, 12
10:01:25,904 INFO [STDOUT] jcr_primaryType = mode:root of type java.lang.String, 12
10:01:25,904 INFO [STDOUT] jcr_score = 1.0 of type java.lang.Double, 8
10:01:25,904 INFO [STDOUT] mode_depth = 0 of type java.lang.Long, -5
10:01:25,904 INFO [STDOUT] mode_localName = of type java.lang.String, 12

But when plain ModeShape JDBC driver is used then all columns are of type String even of non-string values
10:01:25,063 INFO [STDOUT] jcr:primaryType = mode:root of type java.lang.String, 12
10:01:25,064 INFO [STDOUT] jcr:path = / of type java.lang.String, 12
10:01:25,064 INFO [STDOUT] jcr:name = of type java.lang.String, 12
10:01:25,064 INFO [STDOUT] jcr:score = 1.0 of type java.lang.String, 12
10:01:25,064 INFO [STDOUT] mode:localName = of type java.lang.String, 12
10:01:25,064 INFO [STDOUT] mode:depth = 0 of type java.lang.String, 12

ModeShape JDBC driver should use sensible datatypes too.