named-query

问题 I have a method in Dao Class that returns List<Object[]> back and I am using named Query public List<Object[]> getListByCustomer(Session session, int customerId, List<Integer> strIds) { Query namedQuery = session.createSQLQuery(QueryConstants.EXPORT); namedQuery.setParameter("customer", customerId); namedQuery.setParameter("stringId", strIds); List<Object[]> objects = namedQuery.list(); return objects; } I want to pass List<Integer> strIds in stringId into the named query as follows : public

问题 Pre-compiled queries are compiled and cached in advance by DB vendor (like oracle,sql server etc) so that they can be faster for successive calls like prepared statement. In Hibernate Named queries are said to be pre-compiled at web server start up. Does it means all queries are fired at server startup itself so that they can be pre-compiled by DB vendor or pre-compilation has different meaning in hibernate context? 回答1: The Hibernate Named queries are expressed in an object query language

问题 Pre-compiled queries are compiled and cached in advance by DB vendor (like oracle,sql server etc) so that they can be faster for successive calls like prepared statement. In Hibernate Named queries are said to be pre-compiled at web server start up. Does it means all queries are fired at server startup itself so that they can be pre-compiled by DB vendor or pre-compilation has different meaning in hibernate context? 回答1: The Hibernate Named queries are expressed in an object query language

问题 How do we specify LockMode in EJB3 Persistence NamedQuery? I want to add Pessimistic LockMode to my existing select so that I can update if necessary but surprisingly Query object doesnot have setLockMode(xxx) method ( My understanding was if JPA, asubset of EJB3 persistence, exposes setLockMode, EJB3 persistence should have the method available too). Query query = em.createNamedQuery("findOptoutStudent"); query.setParameter("optoutIndicator", optoutIndicator); List<Student> students = query

问题 I have this: class Parent { String name static hasMany = [children: Child] } class Child { String name } And I want to find all the parents that have a child named "Tom" and another one named "Sam". id | parentName --------------- 1 | Peter 2 | Joe 3 | Ann id | childName --------------- 1 | Tom 2 | Sam idParent | idChild --------------- 1 | 1 2 | 2 3 | 1 3 | 2 In the example, it will be Ann. I've tried this: static namedQueries = { findParents{nameList -> children{ nameList.each{childName->

问题 I want to run below query of haversine formula as NamedQuery but I don't know how to correct it. set @orig_lat = 37.334542; set @orig_lon = -121.890821; set @dist = 10; select *, 3956 * 2 * ASIN(SQRT(POWER(SIN((@orig_lat - abs(mlatitude)) * pi() / 180 / 2), 2) + COS(@orig_lat * pi() / 180) * COS(abs(mlatitude) * pi() / 180) * POWER(SIN((@orig_lon - mlogitude) * pi() / 180 / 2), 2))) as distance from user_gps_location having distance < @dist ORDER BY distance I run this query into mysql and it

问题 I have 3 beans: Organization, Role, User Role - Organization relation - @ManyToOne Role - User relation - @ManyToMany Organization : @Entity @Table(name = "entity_organization") public class Organization implements Serializable { private static final long serialVersionUID = -646783073824774092L; @Id @GeneratedValue(strategy = GenerationType.TABLE) Long id; String name; @OneToMany(targetEntity = Role.class, mappedBy = "organization") List<Role> roleList; ... Role : @Entity @Table(name =

问题 Say I have a Person model (Java class and Database table) which has columns/fields like name, age, gender, height, weight. Now there are 2 possibilities 1) I would need the entire column data..so i would have the named query as; @NamedQuery(name = "Person.findAll", query = "Select p from Person WHERE ..." 2) I need only specific column data..so i would have the named query as; @NamedQuery(name = "Person.findSpecific", query = "Select p.name, p.age from Person WHERE ..." In the first case, if

问题 I have a jpa (openjpa-2.2.1) namedquery that has some hardcoded literals (ex: a.status <> 'X') - the problem is at runtime the generated query is actually a prepared statement (a.status <> ?) Is there a way to force JPA run the query as is? (i would like to keep it as namedquery, not implement it as native query or other ways) I would like to run the query as is because of performance reasons - the static query runs in a db client in about 2 seconds while the prepared statement fired from

问题 I am needing to create a named-query, and use it with one of the maps, that i currently have defined as a fluent map. is it possible to continue using the fluent map, and be able to create the named-query dynamically in code? or, is switching to a hbm map the only option? 回答1: Maybe I'm misreading the question, but you don't have to switch to hbm mapping completely. You could continue to use fluent NHibernate to map classes and use hbm for named queries only. In your configuration, you'd then