ObjectDB Database Search

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.AbstractQuery AbstractQuery distinct (    boolean distinct ) Specify whether duplicate query results are eliminated. A true ... . If distinct has not been specified, duplicate results must be retained. Parameters: distinct

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.Subquery Subquery distinct (    boolean distinct ) Specify whether duplicate query results are eliminated. A true value will cause duplicates to be eliminated. A false value will cause duplicates to be retained. If distinct

), but they are more lightweight, are built faster, and consume less memory. SELECT DISTINCT Queries that use ... "euro" more than once. Duplicate results can be eliminated easily in JPQL by using the DISTINCT keyword: SELECT DISTINCT c.currency FROM Country AS c WHERE c.name LIKE 'I%' The only difference between

;  String q1 = "select distinct s_location "          ... ;   q1 = "select distinct s.location "          ... ;   String q2 = "select distinct s.location "        

hi, How can I realize multi selection with the criteria api concerning distinct ? I.e. doing something like SELECT DISTINCT $1, $2 wouldn't work because I do only have something like criteria.multiselect(...) and nothing like builder. distinct (selection) so that I could do something like criteria

Hi, I'm getting a NullPointerException thrown on using DISTINCT . The query works fine if I don't have distinct . However thats NOT a solution as the code generating the query is used for other queries, and some of them do need the distinct . Its only a simple query: QUERY: SELECT DISTINCT $1 FROM

I observed that on new ObjectDb v.2.6.4.b10 query below causes internal exception SELECT DISTINCT $1 FROM Pa3DictionaryItem $2 JOIN $2.values $1 WHERE ($2.namespace == 'com.anritsu.pa3.ttcn3' AND $2 ... Could you comment this? Raised issue: Issue #1176  - DISTINCT key causing internal exception on 2.6.4

, CURRENT_TIME, CURRENT_TIMESTAMP,DELETE, DESC, DISTINCT , ELSE, EMPTY, END, ENTRY, ESCAPE, EXISTS, FALSE

( select , distinct , multiselect , array , tuple , construct ) Criteria FROM ( from , join , fetch

query Returns: subquery join. Since: Jakarta Persistence (JPA) 1.0 Subquery distinct ( boolean distinct ) Specify whether duplicate query results are eliminated. A true value will cause duplicates to be eliminated. A false value will cause duplicates to be retained. If distinct has not been specified

CriteriaQuery . Public Instance Methods CriteriaQuery distinct ( boolean distinct ) Specify whether duplicate ... will cause duplicates to be retained. If distinct has not been specified, duplicate results ... AbstractQuery. distinct Parameters: distinct - boolean value specifying whether duplicate results

Public Instance Methods AbstractQuery distinct ( boolean distinct ) Specify whether duplicate query ... will cause duplicates to be retained. If distinct has not been specified, duplicate results must be retained. Parameters: distinct - boolean value specifying whether duplicate results must be eliminated from

Expression countDistinct ( Expression x ) Create an aggregate expression applying the count distinct operation. Parameters: x - expression representing input value to count distinct operation Returns: count distinct expression. Since: Jakarta Persistence (JPA) 1.0 CriteriaDelete createCriteriaDelete

{ entityManager.close(); } Each EntityManager instance is associated with a distinct persistence context ... , but a distinct Java object identity. If the given entity is detached, the returned entity has the same

I observed that on new ObjectDb v.2.6.4.b10 query below causes internal exception SELECT DISTINCT $1 FROM Pa3DictionaryItem $2 JOIN $2.values $1 WHERE ($2.namespace == 'com.anritsu.pa3.ttcn3' AND $2 ... since it's worked on prev ObjectDb releases, the problems not in '', just remove DISTINCT

of multiple persistent fields or properties, across several entities, and so distinct instances

. The annotated field must not be null, and must hold a distinct value for each value of the enum type

; String query = "SELECT DISTINCT t FROM com.contextspace.datamodel.party.CDI t JOIN t.attributeList attr ... ;    query = "SELECT DISTINCT t FROM com.contextspace.datamodel.party.CDI t JOIN t ... ;      query = "SELECT DISTINCT t FROM com.contextspace.datamodel.party.CDI t

Hello! This query is working fine SELECT DISTINCT $1 FROM ChatHistoryItem $1 JOIN $1.recipient $2 ... "com.objectdb.o.NLV cannot be cast to com.objectdb.o.RSV" SELECT DISTINCT $1 FROM ChatHistoryItem $1 ... I can confirm that the following query causes an exception: SELECT DISTINCT $1 FROM ChatHistoryItem

that are already persisted. em.createQuery(     "SELECT DISTINCT si.page FROM SearchIndex si ... that are already persisted. TypedQuery query = em.createQuery( "SELECT DISTINCT si.page FROM SearchIndex si ... .createQuery( "SELECT DISTINCT p FROM Page p, SearchIndex s1, SearchIndex s2 " +     

an explicit DISTINCT as a workaround until a fix is released: query.select(companyRoot). distinct (true ... . Similarly, selection of only companies may return duplicate objects if DISTINCT is not specified ... queries). THe distinct condition is easy to add to my entities, but not so easy to add

looks like this: SELECT DISTINCT $1 FROM Organisation $1 JOIN $1.attributeList $2 LEFT JOIN $1.parentOrg ... ; "SELECT DISTINCT n1 " +             "FROM Node n1 ... DISTINCT n1 " + "FROM Node n1 LEFT JOIN n1.parent n2 LEFT JOIN n2.parent n3 " + "WHERE n1.nodeId

Hi, Query 1: SELECT DISTINCT $1, $2.lastName AS $O0 FROM com.lexware.vereinsverwaltung.verein.mitglied.Mitglied $1 LEFT JOIN $1.profile $2 ORDER BY UPPER($2.lastName) Correctly returns all the different lastName's for each $1 Now the same but with upper SELECT DISTINCT $1, UPPER($2.lastName) AS

different. Is an "All eager strategy" more efficient that many join fetch ( cartesian product + distinct ... strategy" more efficient that many join fetch (cartesian product + distinct )? So ... "Eager fetch

EntityManagers are in fact distinct objects and not one and the same even if persisted from a single object ... . Original Problem: I have 2 EntityManagers that contain a distinct Entity each: Employee and Paygrade

. Also, we tried a different query today: SELECT DISTINCT NEW com.arunta.base.db.DateExtensionDTO(r.startDate ... List dtoList = new ArrayList(); String qs = "SELECT DISTINCT NEW com.arunta.base.db.DateExtensionDTO

Hi, We have a query that is constructed dynamically, an example is like this: SELECT DISTINCT $1 FROM CDI $1, Organisation $2, Organisation $3 WHERE ((UPPER($1.cdiId) LIKE 'THREAD14%') AND ((($1 ... follows: SELECT DISTINCT $1 FROM CDI $1, Organisation $2, Organisation $3 WHERE (($1.id IN :cdiids

on how to access two different db files or how to distinct tenants in one file from one application? Thanks ... ;is there an example on how to access two different db files or how to distinct tenants in one file

Support Hi, Query I'm running is: SELECT DISTINCT $1 FROM CDI $1 JOIN $1.attributeList $2 JOIN $1

;      .getModelElementsByQuery("select distinct m from " + PoolImpl.class

( issue #142 ). Fixed a bug in distinct queries (duplicates due to bad optimization). Fixed a bug in

DISTINCT m FROM Person m LEFT OUTER JOIN m.answers answers LEFT OUTER JOIN answers.persons likedPersons

then this is normal for JOIN FETCH and you can remove duplication by using SELECT DISTINCT . support Support

yet? support Support it is actually a simple query: select distinct m from ArchitectureImpl m

query: (version 2.7.6 it takes 47 ms, version 2.8.0_02 it takes 700 ms): SELECT DISTINCT o.parentNode ... .ArrayIndexOutOfBoundsException: 2' exception on executing this query what we never had before: SELECT DISTINCT o from ... to go the direction it goes in 2.7.6 ?): SELECT DISTINCT o from ObjectNode o join o.properties p1 join o

We're creating a simple selection ( distinct ) including an order clause. When watching the created criteria in debugger we get the correct expression: SELECT DISTINCT $1 FROM MyEntity $1 WHERE ((TYPE ... .objectdb.o.UserException: Invalid order expression '$2' for distinct results at com.objectdb.o.MSG.d

This query SELECT DISTINCT $1 FROM com.lexware.vereinsverwaltung.verein.mitglied.Mitglied $1 LEFT ... which has worked just fine before!!! See this more simple query (no collection and the such) SELECT DISTINCT $1 ... check for map return first as there might be null values): SELECT DISTINCT $1 FROM com.lexware

. What we can report is: using a reference query (you have our test db) select distinct o from ObjectNode o join o ... : select distinct o from ObjectNode o join o.properties p1 where o.classIdentifier = "(OP)" and ((o ... : select distinct o from ObjectNode o join o.properties p1 where o.classIdentifier = "(OP)" and ((o

.doubleValue = 1) and (p1.name = 'plannedState' and p1.doubleValue 0)   select distinct o from ... " and p2.doubleValue = 0)))   select distinct o from ObjectNode o join o.properties p1  join o ... .doubleValue != 13) and (p1.name = 'plannedState' and p1.doubleValue 0 )   select distinct o from

propertyClassName = propertyClass.getName(); String query = "SELECT DISTINCT property.uid FROM ... , if I add an unless condition. That means the following query don't works: "SELECT DISTINCT ... DISTINCT property.uid FROM CovPropImpl AS property, CovRecImpl AS record WHERE 3 4 AND property.uid MEMBER

one might think of: SELECT DISTINCT $1, UPPER($1.name) AS $O0 FROM com.quasado.foundation.contact ... previously.. alex quasado Alexander Adam Note: Without order by works perfectly: SELECT DISTINCT $1

(Unknown Source)   for that query: SELECT DISTINCT a from Action a WHERE a.objectsInCharge

distinct databases concurrently? If not and you only have one database, try to build

This is the message I get for attached db and this query: SELECT DISTINCT $1 FROM com.lexware.vereinsverwaltung.verein.mitglied.Mitglied $1 WHERE ((($1.qubletID=278) AND NOT (((com.lexware.vereinsverwaltung.abrechnung.api.model.mitglied.MitgliedDebitorenKontoFragment) $1.qubletFRAGMENTMAP.get('com

We have an issue with following query: SELECT DISTINCT instance, instanceEntryArtifactSet, artifact FROM com.btc.ep.engine.bl.internal.dmos.EngineInstanceImpl AS instance JOIN instance.artifacts AS instanceEntryArtifactSet , com.btc.ep.engine.bl.internal.dmos.ArtifactImpl AS artifact LEFT JOIN

Added support of report generation using BIRT . Fixed a bug in query optimization of DISTINCT . Fixed a bug in keeping removed entity object in the L2 cache. Fixed orphan removal of owner entity object in bidirectional relationship. Fixed an "Attempt to persist a reference to a non managed instance

This is the query on the attached db (run in explorer): SELECT DISTINCT $1 FROM com.quasado.foundation.warehouse.payment.Payment $1 LEFT JOIN $1.receivable $2 WHERE (( ((($2 IS NOT NULL) AND ($2.receiver.qubletId=22))))) and this is the result: [ObjectDB 2.4.4] Unexpected exception (Error 990

we have queries like (see the database that we handed over to you for other issues) select distinct o from ObjectNode o join o.properties p1 join o.properties p2 where o.classIdentifier = "(OP)" and (o.linkedObjects.classIdentifier = "(TC)" and  o.linkedObjects.objectNameUpper = "MILLING-EL

in using JOIN FETCH with DISTINCT . Fixed Metamodel API's getTypeId  method to support single ID field .

we face performance issues on queries and therefore compared the times of 2 (same) databases, 2.9.0_05, one after adding statistics and one after additional doctor, here are the results: Query : select distinct o from ObjectNode o where (o.classIdentifier = '(RG)' and o.properties.name