Hibernate – My Shitty Code https://myshittycode.com Embracing the Messiness in Search of Epic Solutions Fri, 06 Jan 2023 17:19:30 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.1 https://myshittycode.com/wp-content/uploads/2022/04/cropped-icon-32x32.png Hibernate – My Shitty Code https://myshittycode.com 32 32 205304208 MS SQL Server + Hibernate 5: Incorrect syntax near ‘@P0’ https://myshittycode.com/2017/06/20/ms-sql-server-hibernate-5-incorrect-syntax-near-p0/ https://myshittycode.com/2017/06/20/ms-sql-server-hibernate-5-incorrect-syntax-near-p0/#comments Tue, 20 Jun 2017 16:07:49 +0000 http://myshittycode.com/?p=1048 PROBLEM When upgrading to Hibernate 5, the following exception is thrown:- SOLUTION Change the MS SQL Server dialect from this… … to this …

The post MS SQL Server + Hibernate 5: Incorrect syntax near ‘@P0’ appeared first on My Shitty Code.

]]> PROBLEM

When upgrading to Hibernate 5, the following exception is thrown:-

Caused by: java.sql.SQLException: Incorrect syntax near '@P0'.
	at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:372) ~[jtds-1.3.1.jar:1.3.1]
	at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988) ~[jtds-1.3.1.jar:1.3.1]
	at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421) ~[jtds-1.3.1.jar:1.3.1]

SOLUTION

Change the MS SQL Server dialect from this…

org.hibernate.dialect.SQLServerDialect

… to this …

org.hibernate.dialect.SQLServer2012Dialect

The post MS SQL Server + Hibernate 5: Incorrect syntax near ‘@P0’ appeared first on My Shitty Code.

]]> https://myshittycode.com/2017/06/20/ms-sql-server-hibernate-5-incorrect-syntax-near-p0/feed/ 3 1048 Developing against H2 Database: Lesson Learned https://myshittycode.com/2014/01/09/developing-against-h2-database-lesson-learned/ https://myshittycode.com/2014/01/09/developing-against-h2-database-lesson-learned/#respond Thu, 09 Jan 2014 21:33:53 +0000 http://myshittycode.com/?p=310 While my production database is MS SQL Server, I have been using H2 database for rapid local development. I wrote my DDL scripts as “Transact-SQL” as possible so that I don’t need to maintain multiple DDL scripts for each database. So far, it has been working out great. My web development runs against H2’s file-based […]

The post Developing against H2 Database: Lesson Learned appeared first on My Shitty Code.

]]> While my production database is MS SQL Server, I have been using H2 database for rapid local development. I wrote my DDL scripts as “Transact-SQL” as possible so that I don’t need to maintain multiple DDL scripts for each database. So far, it has been working out great. My web development runs against H2’s file-based database because I want my data to persist until I manually wipe them off.

That said, I also realized that H2 does behavior a little differently from MS SQL Server. For example, I have the following Hibernate’s HQL query:-

public Collection<Request> getRequestsWithMatchingStatus(Collection<String> statusNames) {
    return sessionFactory.getCurrentSession()
            .createQuery("from Request r where r.status.name in (:statusNames)")
            .setParameterList("statusNames", statusNames)
            .list();
}

If statusNames is an empty collection, H2 will work just fine. However, MS SQL Server will throw the following exception:-

Caused by: java.sql.SQLException: Incorrect syntax near ')'.
	at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
	at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)
	at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)

My test cases didn’t catch this error because they run against H2’s in-memory database.

Of course, the fix is as easy as performing a check on the collection size first:-

public Collection<Request> getRequestsWithMatchingStatus(Collection<String> statusNames) {
    if (statusNames.isEmpty()) {
        return new ArrayList<Request>();
    }</code>
<code>
</code>
<code>    return sessionFactory.getCurrentSession()
            .createQuery("from Request r where r.status.name in (:statusNames)")
            .setParameterList("statusNames", statusNames)
            .list();
}

That said, H2 database allows me to do local development really fast, but I also need to make sure I test it against MS SQL Server from time to time before deploying into production.

The post Developing against H2 Database: Lesson Learned appeared first on My Shitty Code.

]]> https://myshittycode.com/2014/01/09/developing-against-h2-database-lesson-learned/feed/ 0 310 Jadira Usertype: Under JDK 6 it may not be possible to handle DST transitions correctly https://myshittycode.com/2013/12/26/jadira-usertype-under-jdk-6-it-may-not-be-possible-to-handle-dst-transitions-correctly/ https://myshittycode.com/2013/12/26/jadira-usertype-under-jdk-6-it-may-not-be-possible-to-handle-dst-transitions-correctly/#respond Thu, 26 Dec 2013 14:51:54 +0000 http://myshittycode.com/?p=277 PROBLEM When saving a Hibernate entity that contains Joda Time object, Jadira UserType throws the following warning:- This warning occurs when using this version:- SOLUTION Upgrade Jadira Usertype to the latest version, and the problem goes away:-

The post Jadira Usertype: Under JDK 6 it may not be possible to handle DST transitions correctly appeared first on My Shitty Code.

]]> PROBLEM

When saving a Hibernate entity that contains Joda Time object, Jadira UserType throws the following warning:-

[WARN ] [JavaTimeZoneWorkaroundHelper] [&lt;clinit>:40] - Under JDK 6 it may not be possible
to handle DST transitions correctly
[ERROR] [JavaTimeZoneWorkaroundHelper] [&lt;clinit>:42] - Running under a Zone that uses
daylight saving time. To avoid incorrect datetimes being stored during DST transition,
either update to JDK 7 or use a Timezone for the JDK without Daylight Saving Time

This warning occurs when using this version:-

<dependency>
    <groupId>org.jadira.usertype</groupId>
    <artifactId>usertype.core</artifactId>
    <version>3.0.0.GA</version>
</dependency>

SOLUTION

Upgrade Jadira Usertype to the latest version, and the problem goes away:-

<dependency>
    <groupId>org.jadira.usertype</groupId>
    <artifactId>usertype.core</artifactId>
    <version>3.1.0.CR10</version>
</dependency>

The post Jadira Usertype: Under JDK 6 it may not be possible to handle DST transitions correctly appeared first on My Shitty Code.

]]> https://myshittycode.com/2013/12/26/jadira-usertype-under-jdk-6-it-may-not-be-possible-to-handle-dst-transitions-correctly/feed/ 0 277 Hibernate + Joda Time: Auto Registering Type https://myshittycode.com/2013/12/25/hibernate-joda-time-auto-registering-type/ https://myshittycode.com/2013/12/25/hibernate-joda-time-auto-registering-type/#comments Thu, 26 Dec 2013 01:30:19 +0000 http://myshittycode.com/?p=274 OVERVIEW Jadira Usertype is required when using Joda Time with Hibernate 4. The Joda Time objects are annotated accordingly in the Hibernate entity, and they looks something like this:- PROBLEM This solution works, but it is rather tedious because I can never remember the actual @Type to write, thus I always end up copying and […]

The post Hibernate + Joda Time: Auto Registering Type appeared first on My Shitty Code.

]]> OVERVIEW

Jadira Usertype is required when using Joda Time with Hibernate 4. The Joda Time objects are annotated accordingly in the Hibernate entity, and they looks something like this:-

@Entity
@Table(name = "person")
public class Person implements Serializable {

    private static final long serialVersionUID = 1L;

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    @Column(name = "personId")
    private Long id;

    @Column
    private String name;

    @Column
    @Type(type = "org.jadira.usertype.dateandtime.joda.PersistentLocalDate")
    private LocalDate birthDate;

    @Column
    @Type(type = "org.jadira.usertype.dateandtime.joda.PersistentLocalDateTime")
    private LocalDateTime createdDatetime;

    // getters and setters
}

PROBLEM

This solution works, but it is rather tedious because I can never remember the actual @Type to write, thus I always end up copying and pasting it from past project code.

Further, that additional annotations clutter up my otherwise beautiful code.

SOLUTION

Jadira Usertype provides a clean way to auto register these Joda Time object types.

In the Hibernate configuration, add the following line:-

<bean id="sessionFactory" class="org.springframework.orm.hibernate4.LocalSessionFactoryBean">
    <property name="dataSource" ref="dataSource"/>

    <property name="hibernateProperties">
        <props>
            <prop key="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</prop>
            <prop key="hibernate.show_sql">false</prop>
            <prop key="jadira.usertype.autoRegisterUserTypes">true</prop>
        </props>
    </property>
    <property name="packagesToScan">
        <list>
            <value>com.choonchernlim.project.entity</value>
        </list>
    </property>
</bean>

Now all @Type annotations can be safely removed from the Hibernate entity:-

@Entity
@Table(name = "person")
public class Person implements Serializable {

    private static final long serialVersionUID = 1L;

    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    @Column(name = "personId")
    private Long id;

    @Column
    private String name;

    @Column
    private LocalDate birthDate;

    @Column
    private LocalDateTime createdDatetime;

    // getters and setters
}

The post Hibernate + Joda Time: Auto Registering Type appeared first on My Shitty Code.

]]> https://myshittycode.com/2013/12/25/hibernate-joda-time-auto-registering-type/feed/ 1 274 Hibernate: Migrating from XML-Based Configuration to Annotation-Based Configuration https://myshittycode.com/2013/10/21/hibernate-migrating-from-xml-based-configuration-to-annotation-based-configuration/ https://myshittycode.com/2013/10/21/hibernate-migrating-from-xml-based-configuration-to-annotation-based-configuration/#respond Mon, 21 Oct 2013 19:30:54 +0000 http://myshittycode.com/?p=153 Overview At some point of time, as your project scope grows, the Hibernate mapping XML files are going to get to a point where it becomes very difficult to maintain. This is where the annotation-based configuration comes in. It took me a few years to convince myself that annotation-based configuration is the way to go. […]

The post Hibernate: Migrating from XML-Based Configuration to Annotation-Based Configuration appeared first on My Shitty Code.

]]> Overview

At some point of time, as your project scope grows, the Hibernate mapping XML files are going to get to a point where it becomes very difficult to maintain. This is where the annotation-based configuration comes in. It took me a few years to convince myself that annotation-based configuration is the way to go. Change is hard, yet necessary.

This tutorial covers the following:-

  • Upgrade Hibernate from 3.x to 4.x.
  • Configure Spring-Hibernate integration to replace XML-based configuration with annotation-based configuration.
  • Configure Joda-Time to work properly in Hibernate 4.
  • Activate @Transactional instead of relying on AOP-based transaction.

Maven Dependencies

Change the Hibernate dependency version from 3.x to 4.x. On top of that, add org.jadira.usertype:usertype.core:[version] dependency to get Joda-Time to work properly with Hibernate 4.

Hibernate 3.x

<dependency>
    <groupid>org.hibernate</groupid>
    <artifactid>hibernate-core</artifactid>
    <version>3.6.9.Final</version>
</dependency>
<dependency>
    <groupid>joda-time</groupid>
    <artifactid>joda-time</artifactid>
    <version>2.3</version>
</dependency>
<dependency>
	<groupid>joda-time</groupid>
	<artifactid>joda-time-hibernate</artifactid>
	<version>1.3</version>
</dependency>

Hibernate 4.x

<dependency>
    <groupid>org.hibernate</groupid>
    <artifactid>hibernate-core</artifactid>
    <version>4.2.6.Final</version>
</dependency>
<dependency>
    <groupid>joda-time</groupid>
    <artifactid>joda-time</artifactid>
    <version>2.3</version>
</dependency>
<dependency>
	<groupid>joda-time</groupid>
	<artifactid>joda-time-hibernate</artifactid>
	<version>1.3</version>
</dependency>
<dependency>
    <groupid>org.jadira.usertype</groupid>
    <artifactid>usertype.core</artifactid>
    <version>3.1.0.CR8</version>
</dependency>

By the way, if you don’t know what Joda-Time is or haven’t use it by now, then you should be spanked by the Date God. With that added dependency, the @Type for date field will look a little different ( see here for more info ):-

@Entity
@Table(name = "MrMeow")
public class MrMeow implements Ideable, Serializable {
	...

	@Column
	@Type(type = "org.jadira.usertype.dateandtime.joda.PersistentLocalDate")
	private LocalDate whenMeowed;
}

Spring Integration

Hibernate 3.x

This configuration uses Hibernate XML mapping files to configure mappings between the domain objects and the database tables. Further, AOP is used to configure the transaction.

<bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
    <property name="dataSource" ref="dataSource">
    <property name="configLocation" value="classpath:hibernate.cfg.xml">
    </property></property>
</bean>

<bean id="transactionManager" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
    <property name="sessionFactory" ref="sessionFactory">
</property></bean>

<tx:advice id="txAdvice">
    <tx:attributes>
        <tx:method name="*" propagation="REQUIRED">
    </tx:method></tx:attributes>
</tx:advice>

<aop:config proxy-target-class="true">
    <aop:advisor pointcut="execution(* myproject..*.*(..))" advice-ref="txAdvice">
</aop:advisor></aop:config>

Hibernate 4.x

This configuration scans myproject.domain package, which contains all Hibernate annotated domain classes. Further, it activates @Transactional so that you can place it in your code to manage the transaction.

<tx:annotation-driven transaction-manager="transactionManager"/>
    
<bean id="transactionManager" class="org.springframework.orm.hibernate4.HibernateTransactionManager">
    <property name="sessionFactory" ref="sessionFactory"/>
</bean>

<bean id="sessionFactory" class="org.springframework.orm.hibernate4.LocalSessionFactoryBean">
    <property name="dataSource" ref="dataSource"/>

    <property name="hibernateProperties">
        <props>
			<!-- Configure your Hibernate dialect  -->
            <prop key="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</prop>
            <prop key="hibernate.show_sql">false</prop>
        </props>
    </property>
    <property name="packagesToScan">
        <list>
			<!-- Configure your domain package -->
            <value>myproject.domain</value>
        </list>
    </property>
</bean>

web.xml

Change filter class for OpenSessionInViewFilter.

Hibernate 3.x

<filter>
    <filter-name>hibernateFilter</filter-name>
	<filter-class>org.springframework.orm.hibernate3.support.OpenSessionInViewFilter</filter-class>
</filter>
<filter-mapping>
    <filter-name>hibernateFilter</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>

Hibernate 4.x

<filter>
    <filter-name>hibernateFilter</filter-name>
    <filter-class>org.springframework.orm.hibernate4.support.OpenSessionInViewFilter</filter-class>
</filter>
<filter-mapping>
    <filter-name>hibernateFilter</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>

Domain Classes

Finally, time to annotate your Hibernate domain classes!

Helpful Note

Please make sure you don’t have JPA 1.x in your classpath in the first place. Read java.lang.NoSuchMethodError: javax/persistence/OneToMany.orphanRemoval()Z for more information.

The post Hibernate: Migrating from XML-Based Configuration to Annotation-Based Configuration appeared first on My Shitty Code.

]]> https://myshittycode.com/2013/10/21/hibernate-migrating-from-xml-based-configuration-to-annotation-based-configuration/feed/ 0 153