Update:
I have found via the debugger that there is indeed a behavioural change
between 1.4.191 and 1.4.192. The jdbcTemplate from Spring uses in the end
the "resultSet.getObject(index, requiredType)" method. In 1.4.191, this
throws an AbstractMethodError, which Spring handles by calling another
method. In 1.4.192, this no longer throws this exception, but the method in
H2 returns null.
The org.h2.result.LocalResult has 1 row with 1 value with a ValueBytes
object of 16 bytes (representing a UUID).
Should this be considered a bug in H2 1.4.192 ?
regards,
Wim
Op dinsdag 27 september 2016 17:21:39 UTC+2 schreef Wim Deblauwe:
>
> Hi,
>
> I am using H2 1.4.191 (Pulled in via Spring Boot 1.3.5). I wanted to try
> to upgrade to Spring Boot 1.3.8 (which uses H2 1.4.192 by default), but one
> of my unit tests suddenly fails. I managed to make it work again by
> explicitly going back to H2 1.4.191 with Spring Boot 1.3.8. If I use H2
> 1.4.192 with Spring Boot 1.3.5, then the test also failed. So something
> must have changed in 1.4.192 which makes it fail.
>
> I am using Spring Data and the unit test uses:
>
> jdbcTemplate.queryForObject("SELECT image_id FROM game", Object.class)
>
> This returns a non-null value using 1.4.191 and a null value using 1.4.192.
>
> I know this is very little info to go by, but maybe it rings a bell with
> somebody?
>
> regards,
>
> Wim
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
