18 | Query results are not up to date for entities, not primitivesWhen using the CriteriaBuilder to query, the loaded list are not refreshed according to the latest updates. But, when using the JPQL Query, the list are refreshed, and, when I querying for primitive ... side does not any diference. The problem is only solved when changing the query mode, from |
18 | Queries are slow on a large database and there are performances issues. I am doing small queries and they take much longer than I expect, i.e.: Get the total number of entries Get 25 consecutive entries (i.e. 0-25) Get one specific entry On average each query ... use such query: Query query = pm.newQuery(MessageImpl.class, "this.logTestRunId |
18 | How to convert a boolean to an int in the query?How to convert a boolean to an int in the query? I have five parameters of type boolean in ... , approvePhoneNumber, .... because the parameters equivalent. I want to sort them in the query by their sum ... queries. It is possible to add this to ObjectDB in future versions, but using a pre-calculated |
18 | query hintsome years ago there was a chat around query hints http://www.objectdb.com/issue/2417 we are currently trying that with the latest version but we do not see that our hint is used this is the query ... )) [[objectdb.query-plan-text=index(ctso['(TC)'->'(TC)']] but the index that is in the hint is not |
18 | slow performance for a complex queryHi, We have a query that is constructed dynamically, an example is like this: SELECT DISTINCT $1 ... ')))) I've also tried running the CDI query first and passing the results into the organisation query as ... uploaded for issue http://www.objectdb.com/database/forum/350 This query in both variations takes over 3 |
18 | First query takes 4+ minutes to complete query that we run on the DB which contains about 320,000 records of a single type of object. SQLite ... to the query that we run). @Entity(name="RecordingMetaData") @SequenceGenerator( name ... is a single new object and is wrapped in a transaction. 2. The 2nd EntityManager runs the queries |
17 | Help with 'not like/lower' queryHi all, Honestly, I'm fairly new with JPA2 Criteria queries - but as far as code effort goes, it has saved me a bit of pain. I'm writing a dynamic query builder (only 1 level deep for basic entities) - but even though I get most queries to work, I am getting the following error. This is using |
17 | possible index required for improving query performance; } With the following query: TypedQuery<BaseObject> query = em().createQuery( "SELECT r.party FROM Relationship r ... =RelationshipType."+type.toString(), BaseObject.class); query.setParameter("otherParty_id", otherParty); query.setParameter("pclass", partyClass); We have noticed that this query slows down in |
3 | InternalException when using MEMBER OF on a large list in a queryHello, we get when executing a query with MEMBER OF on a large list the following InternalException ... ) (... more see attached Image) Our query looks like this: String recordClassName = CoverageRecordImpl.class.getName(); String propertyClassName = propertyClass.getName(); String query = "SELECT DISTINCT property.uid |
3 | ClassCastException thrown when running count queryHello! Attached you find a full stacktrace. The query was: SELECT COUNT(t) FROM Position t ... for the fields in the query. Log of the query execution using DEBUG logging level. support Support ... and run the query below it will crash with the exception in crash.txt. select p from Position p |
