getTable throws UnexpectedNullValueException

[lauris]

Today I encountered a bug when using getTable method.

Let's assume the following table structure in MySQL:

CREATE TABLE `test_table` (
  `some_setting` tinyint(1) NOT NULL DEFAULT '1'
)

And then try to access table like this (e.g., to get meta data and column list):
db.getTable("test_table").get

First you will get ResultSetExtractorException exception:

Failed to retrieve value because **null**. If you're using SQLInterpolation, you may mistake u.id for u.resultName.id.

As you can see the reason of exception is null, which is a bit strange. If you access the real exception e.e that caused this, you actually get scalikejdbc.UnexpectedNullValueException.

After looking through TypeBinder.scala, it made some sense, but I am still confused.

What could be possible fix or workaround for this? I think that ``some_setting tinyint(1) NOT NULL DEFAULT '1' is a legit column and actually quite common.

I think that this bug is related to the change described in #172.

Thanks!

[seratch]

Which version are you using? I guess you're using 1.7.4 or lower version. If so, would you try the latest version (version 1.7.7)? We fixed a similar issue in version 1.7.5. b0f02d9

[lauris]

I was using 1.7.5 and just upgraded to 1.7.7, but the issue still remains.

"org.scalikejdbc" %% "scalikejdbc" % "1.7.7",
"org.scalikejdbc" %% "scalikejdbc-interpolation" % "1.7.7"

[lauris]

Tried with 2.0.0-RC3 too, same result.

[seratch]

Thanks. I just fixed this issue on both of 1.x and develop branch.

ScalikeJDBC 2.0.0 will be out within days and we'll release 1.7.8 too at the same time.

[lauris]

Thanks! Is it possible to use this fix right away by referencing the commit in build.sbt?

[seratch]

Is it possible to use this fix right away by referencing the commit in build.sbt?

I've never done. Maybe git clone & sbt publishLocal is better.

I just published the latest version as 1.7.8-SNAPSHOT (Sonatype snapshots repository). Try it out.