Temporal annotation
Note:
Maven dependencies used all over JPA tutorials same. Please follow "Setting up Project" section to understand about project configuration. persistence.xml and other code files reused from How to Persist an Entity in data base using JPA? Each Sample application from download includes SQL file also.
Maven dependencies used all over JPA tutorials same. Please follow "Setting up Project" section to understand about project configuration. persistence.xml and other code files reused from How to Persist an Entity in data base using JPA? Each Sample application from download includes SQL file also.
-
@Temporal annotation must be specified for persistent fields or properties of type java.util.Date and java.util.Calendar. It may only be specified for fields or properties of these types.
- @Temporal annotation solves the one of the major issue of converting the date and time values from Java object to compatible database type and retrieving back to the application.
- JPA supports TemporalType.TIMESTAMP, TemporalType.DATE, TemporalType.TIME.
- These types are equivalent of java.sql.Timestamp, java.sql.Date, java.sql.Time.
@Temporal Mapping Code Example :
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
@Entity(name="USER") public class User { @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name = "ID") private Long id; @Column(name="USER_NAME") private String userName; @Column(name="PASSWORD") private String password; @Temporal(value=TemporalType.TIMESTAMP) @Column(name="CREATED_TIME") private Date creationTime; @Temporal(value=TemporalType.TIMESTAMP) @Column(name="UPDATED_TIME") private Date updatedTime; @Temporal(value=TemporalType.DATE) @Column(name="DOB") private Date dateofBirth; @Enumerated(value=EnumType.STRING) @Column(name="USER_TYPE") private UserType userType; |
- From the above snippet line numbers 15,19,23 describes the mapping of Temporal type to the Entity.
- @Temporal annotation more useful to convert specific type either TimeStamp or Time or Date.
Test Code :
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
public static void main( String[] args ) { EntityManagerFactory emf = null; EntityManager entityManager = null; EntityTransaction transaction = null; try{ emf = Persistence.createEntityManagerFactory("jbd-pu"); entityManager = emf.createEntityManager(); transaction = entityManager.getTransaction(); transaction.begin(); User user = new User(); user.setUserName("mike"); user.setPassword("password"); // Setting Current Date user.setCreationTime(new Date()); user.setDateofBirth(new Date()); user.setUserType(UserType.EMPLOYEE); entityManager.persist(user); transaction.commit(); }catch(Exception e){ transaction.rollback(); }finally{ entityManager.close(); emf.close(); } } |
Download Application –
JPA-Temporal.zip (11 KB)
[…] ¿Qué Date resolver? Espero java.util.Date (correcta) y no java.sql.Date? La simple razón es que, al escribir entidades JPA está tratando de hacer un mapa de sus propiedades de entidad a la base de datos de las columnas (y tipos) y java.sql.Date ya está asignada tipo. Por lo que debe utilizar java.util.Date. Por favor, también tenga en cuenta que, por ejemplo, p:calendar (PrimeFaces) es que requieren java.util.Date y no java.util.Calendar (que me topé con él por mí mismo). Se refieren a: javabydeveloper.com/temporal […]
[…] Ce n' Date résoudre? J'espère java.util.Date (correct) et pas java.sql.Date? La simple raison est que, quand vous écrivez des entités, la JPA est d'essayer de mapper les propriétés d'entité de colonnes de base de données (et de genre) et java.sql.Date est déjà mappé type. Si vous devez utiliser java.util.Date. Veuillez également noter que, par exemple, p:calendar (PrimeFaces) exige de la java.util.Date et pas java.util.Calendar (je suis tombé sur ça par moi-même). Voir: javabydeveloper.com/temporal […]