ObjectDB Database Search

. join ( ) ; } catch ( InterruptedException e ) {     e . printStackTrace ... .     backupThread . start ( ) ;     backupThread . join ... of the inner catch block.   jakab Gergely Jakab Maybe the catch block is executed

INNER JOIN c.addresses ORDER BY SIZE(c.addresses) 0 ? CONCAT(c.addresses[0].street + c.addresses[1 ... this query: SELECT c, a FROM Customer INNER JOIN c.addresses a ORDER BY a.street WHERE a.active ... itself... Alex quasado Alexander Adam Maybe something like: SELECT c, a FROM Customer LEFT JOIN c.addresses

Jakarta Persistence (JPA) Annotation Type jakarta.persistence.DiscriminatorColumn Implemented Interfaces: Annotation Target: Type Specifies the discriminator column for the SINGLE_TABLE and JOINED inheritance mapping strategies . The mapping strategy and discriminator column are only specified

and the persistence context has been joined to it, will be marked for rollback. See Also: EntityManager

, if one is active and the persistence context has been joined to it, will be marked for rollback

; + "left join s.location as s_location "            ... ; + "left join s.location as s_location "            ... ;  + "left join s.location as s_location "          

defined as inner static classes. support Support ??? What IDE you use? .persist() is in URIReader

. So...it was like the query received Type.BAD as parameter. This happens regardless of Type being an inner

is happening again, although with different stacktrace (no inner exception is shown) and it is not

thread was trying to join another thread and it got stuck in that state for hours. "WebSocket ... . join (java.base@21.0.1/Thread.java:2078) at java.lang.Thread. join (java.base@21.0.1/Thread.java:2154 ... .Object.wait(java.base@21.0.1/Object.java:366)     at java.lang.Thread. join (java.base@21

Jakarta Persistence (JPA) Method in jakarta.persistence.PersistenceContext SynchronizationType synchronization (Optional) Specifies whether the persistence context is always automatically synchronized with the current transaction or whether the persistence context must be explicitly joined

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CollectionJoin CollectionAttribute getModel() Return the metamodel representation for the collection attribute. Returns: metamodel type representing the Collection that is the target of the join . Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.SetJoin SetAttribute getModel() Return the metamodel representation for the set attribute. Returns: metamodel type representing the Set that is the target of the join . Since: Jakarta Persistence (JPA) 1.0

other than NONE has been set and there is no transaction or the persistence context has not been joined

and there is no transaction or the persistence context has not been joined to the transaction. Since: Jakarta Persistence (JPA) 1.0

and there is no transaction or the persistence context has not been joined to the transaction. Since: Jakarta Persistence (JPA) 3.2

been joined to the transaction. QueryTimeoutException - if the query execution exceeds the query

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.ListJoin ListAttribute getModel() Return the metamodel representation for the list attribute. Returns: metamodel type representing the List that is the target of the join . Since: Jakarta Persistence (JPA) 1.0

Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.MapJoin MapAttribute getModel() Return the metamodel representation for the map attribute. Returns: metamodel type representing the Map that is the target of the join . Since: Jakarta Persistence (JPA) 1.0

back. TransactionRequiredException - if there is no transaction or the persistence context has not been joined

of a JOIN query: SELECT v FROM Values v JOIN v.step s WHERE s.stepNumber = ? JOIN queries

Why does this NamedQuery only work sometimes? @NamedQuery(name = "ItemDB.getPartial", query = "SELECT i FROM com.model.ItemDB i JOIN i.lstSupplier s WHERE s.strSupNumber LIKE ?1") I use ... ("SELECT i FROM com.model.ItemDB i LEFT JOIN i.lstSupplier s WHERE s.strSupNumber LIKE '%5785483

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

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 ... $O0 FROM com.lexware.vereinsverwaltung.verein.mitglied.Mitglied $1 LEFT JOIN $1.profile $2 ORDER BY

value of  EntityChild , you can try: SELECT e FROM EntityParent e JOIN e.map child WHERE child ... with a parameter which is a collection of strings. SELECT e FROM EntityParent e JOIN e . map key

Greetings ObjectDB team, Suppose I have a collection typed field (list/map/set...) in my persistent object of class X. Can I navigate (as opposed to using JOIN ) to  ... expressions (by using JPA's JOIN or JDO's contains). The array expressions that you wrote are not

.linkedObjects join v$2). Step 5: Process ObjectProperty (v$3) instances (for every result tuple ... .hummingbird.ObjectProperty locating ObjectProperty (v$3) instances that satisfy: (v$1.properties join v$3 ... performance). Complex heavy queries with several JOIN operations require examining large number

; Thread backupThread = backupQuery.getSingleResult();    backupThread. join ();   } catch

with orphan remove = true.   I have joined a simple test for you. Thank you for your help and sorry in

to remove this restrictions. Anyway, you need a license key to remove this restriction. support Joined

to a field in these objects directly. You need to use JOIN in JPA and contains in JDO

("SELECT t FROM TeamA t JOIN t.squad s where s.name='Mark Wahlberg'", TeamA.class); List q7results

@Inheritance(strategy=InheritanceType. JOINED ) // Success for Inheritance Sonsection //@Cache(size=10000

for this specific query due to the use of a combined OR on fields of two entity classes through JOIN (Client

CDI $1 JOIN $1.attributeList $2 WHERE ($2.name='firstname') AND ($2.valueAsString='Alex

am not sure that this is a bug. Your query defines an implicit JOIN (on branches), so selection

We are for a some time using joining the thread ODB-IndexActivation to prevent issues when accessing database without the index been ready. Original Thread: https://www.objectdb.com/forum/2401 Now we've run into issue, that in some database the Index rebuild takes a lot of time (e.g. 20 minutes

JOIN $1.mitgliedschaft $2 LEFT JOIN $2.abteilungen $3 LEFT JOIN $3.abteilung $4 WHERE (((NOT ((($2 ... FROM com.lexware.vereinsverwaltung.verein.mitglied.Mitglied $1 LEFT JOIN $1.mitgliedschaft $2 LEFT JOIN $2.abteilungen $3 LEFT JOIN $3.abteilung $4 WHERE (((NOT ((($2 IS NOT NULL) AND ($3 IS NOT NULL

. What we can report is: using a reference query (you have our test db) select distinct o from ObjectNode o join o ... ) instances that satisfy:    (o.linkedObjects join v$1). [Step 2b] Evaluate fields in ... that satisfy:    (o.properties join v$2). [Step 3b] Evaluate fields in ObjectProperty (v$2

Added initial support of Record entities. Implemented a new query method:  containsAnyKey . Improved field type error and internal error messages. Improved the Doctor output. Fixed a bug in using inner classes for query results. Fixed an error due to to an unused type referencing a deleted

. Join ; import javax.persistence.criteria.Root; public class Test_OrderBy { public static void main ... .createQuery(TestEntity.class);   Root root = query.from(TestEntity.class);   final Join otherJoin = root. join ("other");   query.orderBy(cb.asc(cb.upper((Expression ) (Expression ) otherJoin

Added support of editing enum values in the Explorer. Added logging of type registration . Added error message when using mapped by (inverse) collections and maps of invalid types. Changed JOIN FETCH to act as LEFT JOIN in path expressions. Updated the PDF manual. Fixed a possible deadlock

queries  and/or fetch joins that can preempty data that will be needed in the user interface. [Recommended reading JPA Pro 2: - p.164 to p.168 Working with Detached Entities - p.222 Fetch Joins

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.key == 'TliEvent' AND $1 != '') Query above also worked fine on ObjectDb version 2.6.1.b06 Harman

LEFT OUTER JOIN . Fixed GROUP BY DATE(...) - merging AM and PM into the same date.

Fixed a critical bug in extensive removal operations of large objects. Improved the performance of navigation through an inverse (mapped by) field if the owner field is indexed. Fixed a LEFT OUTER JOIN bug . Fixed a bug in parsing queries with parenthesis followed by NOT . Fixed a bug in running

Hello, we found another query bug: SELECT a FROM ArtifactImpl a LEFT OUTER JOIN a.tcSignal s  WHERE a.startStep.stepNumber = 0  AND (s.name IN ('In1') OR a.tcSignal IS NULL) With 2.7.6_b6 we get the expected three result objects. But with 2.8.0 we get only two result objects

Fixed Java Agent / Java EE / Spring enhancement bug. Fixed a bug in merging detached entity objects. Fixed unexpected  NullPointerException in client server mode. Fixed an exception in AVG query on non numeric values ( issue #107 ). Fixed a bug in handling JOIN queries with primary key fields.

, e.g. using a JOIN query. This is because every element is indexed as a separate index entry

Fixed an issue with viewing class Ids in the Explorer (see issue #2677 ). Fixed a regression bug (in version 2.8.5) in using AS in JOIN ( issue #2666 ). Fixed a connection pool issue related to memory release ( issue #2663 ). Fixed an Enhancer issue in supporting Java 9 modules and packages