 12 | understand that making a query just on entity.id.field1 is efficient. Of course, making a query ... is: what about making a query just on entity.id.field2? I suppose it will not be an efficient query ... indexed. Accordingly queries on field1 (and on both fields) will be fast, and queries on field2 |
12 | query gets no items: SELECT i FROM Item i WHERE :label1 MEMBER OF item.labels AND :label2 MEMBER OF item.labels Is it a bug or JPQL query is wrong? Best regards, Pablo. This seems to be the result of how JPQL queries are converted into SQL like syntax before executing. MEMBER OF is implemented using |
12 | > query = em.createQuery("SELECT m FROM ObjectDbMessagePayload m WHERE m.id = :id", ObjectDbMessagePayload.class);
query.setParameter("id", msg.getId());
List loaded = query ... well (see below). Interestingly the exception is thrown from the find method rather than the query. The application |
12 | How write a query in JPA2 with LEFT JOIN on INNER JOIN?
select a.description, a.id, p1 ... a, action_profile ap1, profile p1, ... and add the constraints in the WHERE clause. But actually your query ... , this is my critera query:
CriteriaBuilder cb = entityManager.getCriteriaBuilder();
CriteriaQuery |
12 | is the producer from DB (based on a query) and I would like to speed it up. I have tried using several entity ... . each query in a thread is running simultaneously - but it looks sometimes the "query threads ... it is coming from some ObjectDB low level I/O settings? Any help on how to speed up query by doing |
12 | are represented in queries by entity names. By default, the entity name is the unqualified name ... . their instances cannot be shared by different entity objects and they cannot be queried directly ... and retrieval is faster). It simplifies queries on dates and ranges of dates. When an entity is stored |
12 | useful when using queries that return large result sets. As an example, consider a real time ... that queries that retrieve all the events of a specified sensor in a specified period are common and return thousands of Event objects. In that case the following primary key can significantly improve query run |
12 | ); In addition, the hint can be set for a specific retrieval operation or query. Releasing ... );
A lock mode can also be set for a query in order to lock all the query result objects. When a retrieval |
12 | , EclipseLink For ObjectDB there is one query in following method, where the full qualified class ... :695)
at at.sciencesoft.db.jpa.DAOjpa.query(DAOjpa.java:326)
at at.sciencesoft.user.User ... - the query works with the simple class name. Breaking down the code for simple example would be little |
12 | :
Query query = pm.newQuery();
query.setResult("count(this)");
query.setClass(myClass);
return (Long) query.execute(); All queries (eg ones with parameters) on the same class fail with the same ... , and the cause is unknown. It happens during cleanup of query execution in a finally block. Maybe |