ObjectDB Database Search
51-66 of 66 resultsjakarta.persistence.TupleElement.getAlias() Jakarta Persistence (JPA) Method in jakarta.persistence.TupleElement String getAlias() Return the alias assigned to the tuple element or null, if no alias has been assigned. Returns: alias. Since: Jakarta Persistence (JPA) 1.0 | |
Entity is not related to ObjectDB, but i get exception from ObjectDB: Could not instantiate entity: granat.dp.domain.entity.psql.DialogNew at org.hibernate. tuple ... ] at org.hibernate. tuple .PojoInstantiator.instantiate(PojoInstantiator.java:136) [hibernate-core-4.0.1.Final.jar:4.0.1.Final] at org.hibernate. tuple .entity.AbstractEntityTuplizer.instantiate | |
query hint tuple of the steps above) ------------------------------------------ [Step 3a] Iterate ... .classIdentifier='(TC)'). Step 4: Process ObjectProperty (p2) instances (for every result tuple ... ='scheduledEndSlot'). Step 7: Process ObjectProperty (p4) instances (for every result tuple of the steps | |
Multi selection and distinct in a criteria query selection element in my tuple selection only? I.e. I don't want to every selection expression | |
Join performance in Objectdb, executing the JOIN may require iteration over 160,000 x 160,000 x 160,000 tuples . The following test | |
Group by date / time; Tuple .class);   | |
Issue with alias execution in managing result elements using Tuple ). This is because the real order of query clauses | |
composite index not used in query)'). Step 3: Process ObjectNode (v$1) instances (for every result tuple of the steps | |
Different behavior for two equal queries.organisation. Step 3: Process IndividualCommunicationInfo (v$2) instances (for every result tuple ... IndividualCommunicationClassification (v$3) instances (for every result tuple of the steps ... .classification. Step 6: Process IndividualPostalAddress (v$4) instances (for every result tuple | |
combined index not used (for every result tuple of the steps above) ------------------------------------------ [Step 4a] Scan ... .linkedObjects join v$2). Step 5: Process ObjectProperty (v$3) instances (for every result tuple ... ='(OP)'). Step 3: Process ObjectProperty (p1) instances (for every result tuple of the steps | |
queries under 2.7.6_4 significantly slower than under 2.7.6) instances (for every result tuple of the steps ... tuple of the steps above) --------------------------------------------- [Step 4a] Scan type com ... ) instances (for every result tuple of the steps | |
Issue with UPPER ? ($4) instances (for every result tuple of the steps ... IndividualPostalAddress ($5) instances (for every result tuple of the steps ... ; (for every result tuple of the steps above) ---------------------------------------------------------- [Step 8a | |
Issue with DISTINCT Select more than on tuple , e.g. if (1,2a) and (1,2b) are both result tuples - only 1 is returned ... .. however, it returns either Object[] or Tuple element result lists and I need only a clean Collection ... and extracting the first part of each tuple element and putting it into my own list.. Isn't there any | |
@FetchGroup in JPA similar to JDO_NAME, "names"); This will be equivalent to query using tuples : TypedQuery query = em.createQuery("select e.firstName, e.lastName FROM Entity e", Tuple .class); But with fetch group you don't have to convert tuples to objects. I know that you can add many constructors to Entity and change query | |
Weird issue with variable naming.persistence.OneToMany; import javax.persistence.Persistence; import javax.persistence. Tuple ; import javax | |
ObjectDB 2.7.5 ). Fixed a ClassCastException in using Tuple .get on a criteria query path ( issue #2200 ). |