Not supported, input parameters are only allowed in the WHERE and HAVING clauses and you cannot use parameters for the ORDER BY clause. Or if I rephrase, you can’t use parameters for columns, only values. So, either: Have as much named queries as possible sort orders Concatenate the ordering string to the query string Use … Read more
To use request scope without Spring MVC, you should declare RequestContextListener in web.xml (see 3.5.4.1. Initial web configuration): <web-app> … <listener> <listener-class> org.springframework.web.context.request.RequestContextListener </listener-class> </listener> … </web-app>
Although answer given by Subhendu Mahanta is correct. But @CollectionOfElements is deprecated. You can use @ElementCollection instead: @ElementCollection @JoinTable(name=”ATTRIBUTE_VALUE_RANGE”, joinColumns=@JoinColumn(name=”ID”)) @MapKeyColumn (name=”RANGE_ID”) @Column(name=”VALUE”) private Map<String, String> attributeValueRange = new HashMap<String, String>(); There is no need to create a separate Entity class for the Map field. It will be done automatically.
Use polymorphism=”explicit” in the class mapping. This will cause queries to return only instances of the named class and not its subclasses. Implicit polymorphism means that instances of the class will be returned by a query that names any superclass or implemented interface or class, and that instances of any subclass of the class will … Read more
I had the same problem. It is related to the id allocating strategies of Hibernate. Whe n you choose GenerationType.SEQUENCE, Hibernate uses HiLo strategy which allocates IDs in blocks of 50 by default. So you can explicitly set allocationSize value like this: @Id @SequenceGenerator(name=”pk_sequence”,sequenceName=”entity_id_seq”, allocationSize=1) @GeneratedValue(strategy=GenerationType.SEQUENCE,generator=”pk_sequence”) @Column(name=”id”, unique=true, nullable=false) public int getId() { return this.id; … Read more
It may be an overkill but have you thought about writing your own CustomIDGenerator which probably subclasses say the AutoGenerator of hibernate and exposes a couple of methods where you can set the id of the next class object to be generated so for example class MyGenerator extends …. { public void setIdForObject(Class clazz, Long … Read more
Assumptions Because I don’t have the reputation yet to post a comment below your question, my answer is based on the following assumptions: The current schema name to be used for the current user is accessible through a Spring JSR-330 Provider like private javax.inject.Provider<User> user; String schema = user.get().getSchema();. This is ideally a ThreadLocal-based proxy. … Read more
The Manning book Java Persistence with Hibernate has an example outlining how to do this in Section 7.2. Fortunately, even if you don’t own the book, you can see a source code example of this by downloading the JPA version of the Caveat Emptor sample project (direct link here) and examining the classes Category and … Read more
Joins can only be used when there is an association between entities. Your Employee entity should not have a field named id_team, of type int, mapped to a column. It should have a ManyToOne association with the Team entity, mapped as a JoinColumn: @ManyToOne @JoinColumn(name=”ID_TEAM”) private Team team; Then, the following query will work flawlessly: … Read more
From an Hibernate point of view, it doesn’t change anything as Hibernate uses the same Hibernate type to represent them. However, as pointed out by Bytecode Ninja, you can’t distinguish the default value of a primitive int 0 from a an assigned 0 while there is no possible ambiguity with a null (a null id … Read more