timmalich/hibernate-types

The Hibernate Types library gives you extra types that are not supported by the Hibernate ORM core.

Introduction

The Hibernate Types repository gives you extra types and general purpose utilities that are not supported by the Hibernate ORM core.

The main advantage of this project is that it supports a broad range of Hibernate versions, spanning from Hibernate 4.1 to Hibernate 5.4.

Features

JSON

Oracle

You should use the JsonStringType to map a VARCHAR2 column type storing JSON.

You should use the JsonBlobType to map a BLOB column type storing JSON.

For more details, check out this article.

SQL Server

You should use this JsonStringType to map an NVARCHAR column type storing JSON.

For more details, check out this article.

PostgreSQL

You should use this JsonBinaryType to map both jsonb and json column types.

For more details, check out this article.

MySQL

You should use this JsonStringType to map the json column type.

For more details, check out this article.

JSON mapping examples

• How to map Oracle JSON columns using JPA and Hibernate
• How to map a Jackson JsonNode to a JSON column
• Java Object to String or Binary JSON column mapping
• How to map JSON collections using JPA and Hibernate
• How to customize the Jackson ObjectMapper used by Hibernate-Types
• How to customize the JSON Serializer used by Hibernate-Types
• How to fix the Hibernate “No Dialect mapping for JDBC type: 1111” issue when mixing JSON types with native SQL queries
• How to fix the column is of type jsonb but expression is of type record or bytea issue

ARRAY

• How to map a PostgreSQL ARRAY to a Java List with JPA and Hibernate
• How to map the PostgreSQL ARRAY to Java Arrays with JPA and Hibernate
• Multidimensional array mapping with JPA and Hibernate
• How to map the HSQLDB ARRAY type with JPA and Hibernate

PostgreSQL Types (e.g. ENUM, INET, HSTORE, RANGE)

• Java Enum to PostgreSQL Enum Type
• How to map the PostgreSQL Inet type with JPA and Hibernate
• How to map a PostgreSQL HStore entity property with JPA and Hibernate
• How to map a PostgreSQL Enum ARRAY to a JPA entity property using Hibernate
• How to map a PostgreSQL Range column type with JPA and Hibernate
• How to map a PostgreSQL Interval to a Java Duration with Hibernate

Generic Types

• How to map java.time.YearMonth to DATE or INTEGER column
• How to map java.time.Year and java.time.Month with JPA and Hibernate
• Character to nullable CHAR column
• ImmutableType utility to simplify UserType implementations

Utilities

Naming Strategy

• CamelCaseToSnakeCaseNamingStrategy - How to map camelCase properties to snake_case column names with Hibernate

DTO Projection and ResultTransformer

• ClassImportIntegrator - How to write a compact DTO projection query with JPA
• ListResultTransformer - The best way to use a Hibernate ResultTransformer
• MapResultTransformer - How to return a Map result from a JPA or Hibernate query

Are you struggling with application performance issues?

Imagine having a tool that can automatically detect if you are using JPA and Hibernate properly. No more performance issues, no more having to spend countless hours trying to figure out why your application is barely crawling.

Imagine discovering early during the development cycle that you are using suboptimal mappings and entity relationships or that you are missing performance-related settings.

More, with Hypersistence Optimizer, you can detect all such issues during testing and make sure you don't deploy to production a change that will affect data access layer performance.

Hypersistence Optimizer is the tool you've been long waiting for!

Training

If you are interested in on-site training, I can offer you my High-Performance Java Persistence training, which can be adapted to one, two or three days of sessions. For more details, check out my website.

Consulting

If you want me to review your application and provide insight into how you can optimize it to run faster, then check out my consulting page.

High-Performance Java Persistence Video Courses

If you want the fastest way to learn how to speed up a Java database application, then you should definitely enroll in my High-Performance Java Persistence video courses.

High-Performance Java Persistence Book

Or, if you prefer reading books, you are going to love my High-Performance Java Persistence book as well.

Installation

Depending on the Hibernate version you are using, you need to add the following dependency:

Hibernate 5.4, 5.3 and 5.2

<dependency>
    <groupId>com.vladmihalcea</groupId>
    <artifactId>hibernate-types-52</artifactId>
    <version>2.9.11</version>
</dependency>

Hibernate 5.1 and 5.0

<dependency>
    <groupId>com.vladmihalcea</groupId>
    <artifactId>hibernate-types-5</artifactId>
    <version>2.9.11</version>
</dependency>

Hibernate 4.3

<dependency>
    <groupId>com.vladmihalcea</groupId>
    <artifactId>hibernate-types-43</artifactId>
    <version>2.9.11</version>
</dependency>

Hibernate 4.2 and 4.1

<dependency>
    <groupId>com.vladmihalcea</groupId>
    <artifactId>hibernate-types-4</artifactId>
    <version>2.9.11</version>
</dependency>

Requirements

• Java version supported by the Hibernate ORM version you are using.
• SLF4J
• Jackson Databind

How to remove the Hypersistence Optimizer banner from the log?

Why the Hypersistence Optimizer banner?

Maintaining this project costs thousands of dollars per year, and, without the support of Hypersistence, this project would have to be abandoned.

The reason why this banner was added is that, when I enabled GitHub donations, no one ever donated a single cent to support this project.

And, spreading the news about the amazing Hypersistence Optimizer tool I'm currently building is much more beneficial for the vast majority of Hibernate projects.

Adding Hypersistence Optimizer to your project

Using Hibernate without Hypersistence Optimizer is highly discouraged, hence the reason for that banner. You can view it as a WARN log message that tells you are risking application performance issues if you don't make sure you use the right JPA mappings and Hibernate configuration properties.

If you want to see why it's a bad idea to use JPA and Hibernate without a tool that inspects your mappings and configurations, check out this video presentation.

So, the easiest way to have the banner removed is to add Hypersistence Optimizer to your project.

Setting the hibernate.types.print.banner=false configuration setting

You can disable the banner by providing the hibernate.types.print.banner=false in either hibernate.properties or hibernate-types.properties file.

For Spring and Spring Boot, this Pull Request is needed to be integrated into Hibernate ORM.

Once this Pull Request is integrated, you could pass the hibernate.types.print.banner=false configuration property from the application.properties file.

So, in the meanwhile, you could vote for the HHH-14020 issue and remind the Hibernate team that you really need that Pull Request to be integrated. Hopefully, it will be added to the project sooner than later.

If can also provide the hibernate.types.print.banner=falsesetting as a Java System property when bootstrapping your Java application:

java -Dhibernate.types.print.banner=false -jar target/application-1.0.0.jar

Will I remove the banner?

I know the banner might be a little annoying. But you know what's even more annoying? Having all those open issues waiting to be fixed.

So, I decided that I would remove the banner only when the vast majority of the currently opened issues were going to be fixed. If you don't have the time to do it, I totally understand that. I don't have the time to do it either. But, I could be paid to do that, and then, you could all benefit from those new features. I estimated the cost for working on all those issues to be around 25000$. If anyone is willing to sponsor the development of this project, don't hesitate to contact me.

If you're wondering why that banner was not removed by now, it's because there are still plenty of issues waiting to be fixed, and that's not the true spirit of open-source software development!

Should you open a GitHub issue asking me to remove the banner?

Disabling this banner takes very little time, so there is no point in opening a GitHub issue to ask me to remove this banner, especially since there's already a pinned GitHub issue explaining how to remove it.

Keep in mind that all issues related to the banner removal will be deleted because I use the GitHub issue feature for technical features only (e.g., enhancements, bug fixing).

In case you think that the banner is unfair and disabling it is too much of an effort for you, then you can also:

• fork the repository
• remove the banner from the source code
• build the project and use your own banner-free version

This project is free as in Libre, not Gratis.

Code of conduct

1. If you don't agree with these Terms and Conditions, you don't have to use the official repository. You are free to fork the repository and manage it as you may wish.
2. Bullying, rudeness, arrogance, or lecturing me about OSS with an utter sense of entitlement are not tolerated and might lead to GitHub account banning.

The only people entitled to say how open source 'ought' to work are people who run projects, and the scope of their entitlement extends only to their own projects.

Just because someone open sources something does not imply they owe the world a change in their status, focus and effort, e.g. from inventor to community manager.

As a user of something open source you are not thereby entitled to anything at all. You are not entitled to contribute. You are not entitled to features. You are not entitled to the attention of others. You are not entitled to having value attached to your complaints. You are not entitled to this explanation.

If you have expectations (of others) that aren't being met, those expectations are your own responsibility. You are responsible for your own needs. If you want things, make them.

Open source is a licensing and delivery mechanism, period. It means you get the source for software and the right to use and modify it. All social impositions associated with it, including the idea of 'community-driven-development' are part of a recently-invented mythology with little basis in how things actually work, a mythology that embodies, cult-like, both a lack of support for diversity in the ways things can work and a pervasive sense of communal entitlement.

-- Rich Hickey

How to start the test environment

cd docker
docker-compose up -d

How to stop the test environment

cd docker
docker-compose down -v

How to get access to database logs

docker logs -f mysql-hibernate-types
docker logs -f postgresql-hibernate-types