@NamedQuery over @NamedNativeQuery

java hibernate annotations hql
Abhi picture Abhi · Dec 19, 2012 · Viewed 20.9k times · Source

Is there any benefit of using @NamedQuery over @NamedNativeQuery in hibernate or vice verse. I cant spot the exact difference or in which context we should use @NamedQuery over @NamedNativeQuery

Thanks in advance.

Answer

Oleksi picture Oleksi · Dec 19, 2012

@NamedNativeQuery lets you write a named SQL query, while @NamedQuery lets you write a named HQL query (or JPQL).

In general, you should prefer to write HQL queries because then you can let Hibernate handle the intricacies of converting the HQL into the various SQL dialects. This will make your job much simpler when you choose to switch DBMS providers.

Related questions

org.hibernate.MappingException: Could not determine type for: java.util.Set

Although this question asked many times and I have already used all the suggestion but still I am getting this error. The User.java is @Entity @Table(name = "USER") public class User implements UserDetails, Serializable { private static final long serialVersionUID = 2…

Read More
Do I need <class> elements in persistence.xml?

I have very simple persistance.xml file: <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.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 …

Read More
Hibernate Annotations - Which is better, field or property access?

This question is somewhat related to Hibernate Annotation Placement Question. But I want to know which is better? Access via properties or access via fields? What are the advantages and disadvantages of each?

Read More