Skip to main content

JPA and Enums

There are different ways of configuring enums inside JPA entity which yields different results.

Let's consider we have this enum

public enum EmpType {
FULL_TIME, PART_TIME;
}

And the entity

@Entity
public class Employee implements Serializable {

private static final long serialVersionUID = 1L;
@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private Long id;
@Column
private String name;
@Enumerated
private EmpType empType;

..
}

To use enum we have to annotate field with @Enumerated

Employee e = new Employee();
e.setId(1L);
e.setName("na");
e.setEmpType(EmpType.FULL_TIME);
em.persist(e);



the above code will save entity as follows
ID EMPTYPE NAME
1 0 na

This is because all the enum's in EmpType are indexed starting from zero, so if we change order or introduce a new enum in middle we lose the context in Employee table.

Instead use this @Enumerated(EnumType.STRING) which save the above entity as

ID EMPTYPE NAME
1 FULL_TIME na

If you are looking for more advance mapping then consider this post
Advance Enums JPA 2.0

Comments

Riccardo Cossu said…
Hello, I use enums quite often and I find using EnumType.String very useful, not only for the fact that I can change the order, but also because sql queries are simpler to write this way and results easier to read (you don't have to lookup the code to know what does that '1' stand for!).

Do you think that theese advantages balance the greater database space use? I actually never ran in a situation where the size of those field is really an issue - a few bytes more by a few thousands record sum up as a few kilobytes after all, but a case with a table with many enums may be different.
checkout this new custom enum value configuration

http://mdshannan1.blogspot.com/2010/09/jpa-20-enums-with-custom-values.html
Riccardo Cossu said…
Yes, it is viable option.
Thanks

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc