Home » Search

About results

21-30 of 200Refresh
Manual
17

Logical Operators in JPQL and Criteria API

the result is FALSE, because one FALSE operand is sufficient for a FALSE result. If one operand is NULL and the other operand is either TRUE or NULL, the result is NULL (unknown). ObjectDB supports ... NULL represents unknown. Therefore, if one operand is NULL and the other operand is TRUE the result
Forum
17

Iterating over large result set

of given size until whole result set is iterated.  What I'm thinking about is some kind of streaming of result set from database without building whole object graph representing fetched data in application ... with a hint "objectdb.result-fetch" set to "LAZY". Another option is to use a report query, i.e
Forum
17

Query results are not up to date for entities, not primitives

CriteriaBuilder to JPQL or from Entity to Primitive. What´s now? This could be the result of getting query results from the cache. There is no difference between criteria queries and string based JPQL queries ... and may result in not being seen by queries: "Updating entity objects in the database using an UPDATE query
Issue
16

DB persist operation results are not available for another Thread/EntityManager immdiately

a query. But there are not any results available. We debugged the problem. Thread B executes the query and prints the results to the console, but there are not results. After that the thread stops ... again. And we get the expected results. Why? It is also possible to insert a Thread.sleep(1000) before executing
Forum
16

Empty query results after JAR creation

.jar", I get either empty results or on some cases a "NoResultException" which appears to report ... but once the Jar File is created and moved to a different folder, the query does not return any results any ... file that can be distributed? Thanks for any help.   Empty results or NoResultException may be caused
Issue
16

Query execution creates a wrong result

Hello, we analysed an unexpected behavior and find out that the result of an Query are wrong ... returns an expected result (one Entity). The second Query is the first Query with an additional WHERE condition. But than we get another (wrong) result.   We used Version 2.6.5 and the BUG is fixed
Issue
16

query only reports 1 result

2.7.2_01 suddenly some queries do only have 1 result even there are more results (you can use the database that you have from #308):   this query gives 1 result even there are a lot more: select o ... .classIdentifier = '(XX)' if you take away the last condition you can see a lot of fitting results
Forum
16

Query with FETCH JOIN returns multiple results instead of one.

with two services, it's returned twice (both results contain the same instance). I believe that such query should return only one result, with fetched service sub-elements, shouldn't it? I am almost sure (but I did not bother to check, sorry!) that JPA+Hibernate would return only one result. Am I wrong
Forum
16

Unexpected COUNT Results

the list with size  1380. This is expected result If we add COUNT operator: b.      SELECT COUNT($1 ... .keyDescriptor.namespace="com.anritsu.pa3") This query returns value 1758. This is not expected result ... results in 1.b and 1.c are not as expected? Why order of conditions (1.c) affects the result? Thanks
Forum
16

@ElementCollection query returning extra result per element in collection

. The issue is that, I'm getting repeated results of the owning entity of an '@ElementCollection ... :p1) AND (($1.conditionOne=:p2))) Got: 1 results - correct ... ) OR ($1.conditionOne=:p3)))) Only expected one result, but got: 2