JSR-310年映射到MySQL中的TINYBLOB

Question

Well, mine is a silly question.

With Hibernate 5.1 (5.2 the same) my Year column is mapped to tinyblob instead of the intuitive int column one would expect. Other JSR-310 columns are successfully mapped.

Eg

@Column(name = "ANNO_PROTOCOLLO", nullable = true)
protected Year annoProtocollo;

@Column(name = "CREATED", nullable = false, updatable = false, insertable = true)
protected LocalDateTime created = LocalDateTime.now();

The first column is mapped to tinyblob but the second is correctly mapped to datetime which is the SQL standard for such values.

Again, my question is silly because nothing prevents me to declare that Year column as an int, but I wanted to understand the reason behind this and if there is a way that takes less than 3 lines of code to map Year to int. Since I need to work on multiple databases, I cannot accept @Column(columnDefinition) and if that is the only solution I will just use Integer and live with that, as I did before

Answer 1

The simple reason is that they didn't provide a specific mapping for Year , so you're getting the default mapping of object serialization to/from bytes, ie a BLOB.

You can implement a custom type to provide a mapping.
See Hibernate Domain Model Mapping Guide - Custom BasicTypes .