ObjectDB Database Search
151-200 of 200 resultsQuery all objects that implements a given interface - is that possible? Hi, I am trying query one of my DB - for all object types that implement a given interface. TypedQuery query = em.createQuery ... variable ('bk') of type Signals.Signal_Interface (error 737) at com.objectdb.jpa.JpaQuery | |
locks on pure query activities that are just doing simple queries (just selects, no update or delete ...) show locks like these (question ... on separate disks you may be able to refer read only queries to replicated slaves. support Support ... We can see that the more threads are doing exactly the same query we step into more and more situations | |
Query to find object from element of a contained collection a multi variable query with JOIN . support Support Thank you for the fast support ... elements by OrderData.items.itemId. I cant get a proper query with MEMBER OF or IN. Does anyone have an idea on how i could formulate that as Typed or CriteriaBuilder query ? Thanks. @Entity | |
Query in JPA2 with LEFT JOIN on INNER JOIN How write a query in JPA2 with LEFT JOIN on INNER JOIN? select a.description, a.id, p1.description ... ; JOIN close is invalid in JPQL. Instead of ON you may include all the variables in ... the WHERE clause. But actually your query may indicate that you model is not optimized for JPA. Instead | |
JPA Query language support in OBjectDB / Sub query or nested Query have given a sample typed query below which fails to work with ObjectDB and it runs very well with the Hibernate/MySQL JPA. We are using Spring Data here. It looks like a problem with Sub query or nested queries where I am using IN clause like below. @ Query ("SELECT product FROM Product product | |
Criteria query error: Unexpected query token.arquillian.spi.ArquillianProxyException: com.objectdb.o._PersistenceException : Unexpected query token ... to see? Or is Criteria a W.I.P? Cheers Willks William It seems that the query is invalid because a SELECT is not specified. Unexpected query token 'FROM' (SELECT is expected) A query with no SELECT | |
Querys slower when execute a query after every persist The test case of the java file attachment persists many entities and executes a query ... requires only 20 sec, but the test requires 100 sec. Why the querys will be more and more slower? In ... more time (i.e. every query execution requires a more expensive flush). Results of your test | |
Cache configuration of database file pages, query programs, query results Are there some possibilities to configure following caches in order to keep cache data for only some important entity types and for the entire life cycle of the EntityManagerFactory. Cache of database file pages. Cache of query programs. Cache of query execution results. btc_es BTC EmbeddedSystems | |
ObjectDB Explorer query error: Unexpected query token 'value' Hi, my entity is named "XXXValue": this has several attributes, one of these is "value". In query tab, if I do "select value from XXXValue", I get the error . I try "select XXXValue.value from XXXValue" and the error is the same. Queries on others attributes work fine. Thanks! luca | |
Query problem after transaction commit to it. The client program can connect to the server and query to get all the records ... [Remarks] 01 Test_Connection: connecting 02 Test_Connection: connected 03 UI: start query [ query ... 05 code= %, desc= % 06 UI: end query 07 UI: start printing result 08 code= A, desc= Good | |
Query results are not up to date for entities, not primitives When 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 ... on update side does not any diference. The problem is only solved when changing the query mode, from | |
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 field | |
query hint some 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 ... .name = 'slots' and p4.doubleValue 0)) [[objectdb. query -plan-text=index(ctso['(TC)'-'(TC | |
IN expression in a Criteria Query, it is written that ObjectDB is 100% compatible with JPA. However, I have problem with this JPQL query ... .employeeEntity = e) ORDER BY e.name with Hibernate, there was no problem with this query , but ObjectDB throws exception: com.objectdb.o.UserException: Unexpected query token 'EXISTS' Second problem | |
slow performance for a complex query Hi, 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 ... for issue http://www.objectdb.com/database/forum/350 This query in both variations takes over 3 | |
First query takes 4+ minutes to complete SELECT query that we run on the DB which contains about 320,000 records of a single type of object ... (related to the query that we run). @Entity(name="RecordingMetaData") @SequenceGenerator( name ... EntityManager runs the queries (JPQL SELECT statements) shown next. Query We test | |
jakarta.persistence.criteria.CriteriaUpdate Methods Root from ( Class entityClass ) Create and add a query root corresponding to the entity ... that is being updated. Parameters: entityClass - the entity class Returns: query root corresponding to the given entity. Since: Jakarta Persistence (JPA) 1.0 Root from ( EntityType entity ) Create and add a query root | |
jakarta.persistence.NamedQuery: Annotation Target: Type Declares a named query written in the Jakarta Persistence query language. Query names are scoped to the persistence unit. A named query may be executed by calling EntityManager.createNamedQuery . The following is an example of the definition of a named query written in | |
jakarta.persistence.Embeddable methods or persistent instance variables . An enum or interface may not be designated as | |
jakarta.persistence.Basic Jakarta Persistence (JPA) Annotation Type jakarta.persistence.Basic Implemented Interfaces: Annotation Target: Method, Field The simplest type of mapping of a persistent field or property to a single database column. The Basic annotation may be applied to a property or instance variable whose type | |
jakarta.persistence.NamedNativeQuery Interfaces: Annotation Target: Type Declares a named native SQL query and, optionally, the mapping of the result of the native SQL query . Query names are scoped to the persistence unit. A named query ... how the native SQL query result set should be interpreted, for example: @NamedNativeQuery( name | |
jakarta.persistence.criteria.CriteriaDelete entityClass ) Create and add a query root corresponding to the entity that is the target of the DELETE ... - the entity class Returns: query root corresponding to the given entity. Since: Jakarta Persistence (JPA) 1.0 Root from ( EntityType entity ) Create and add a query root corresponding to the entity | |
jakarta.persistence.QueryTimeoutException the persistence provider when a query times out and only the statement is rolled back. The current ... (JPA) 1.0 QueryTimeoutException ( Query query ) Constructs a new QueryTimeoutException exception with the specified query . Parameters: query - the query . Since: Jakarta Persistence (JPA) 1.0 | |
JPA Lifecycle Events with the database operation that triggers the event, callback methods must not call EntityManager or Query methods | |
JPA Core Types) and close it upon shutdown. The primary interface for performing CRUD operations, building queries | |
What is ObjectDB? ObjectDB is an Object Oriented Database Management System (ODBMS). It provides all the standard database management services (storage and retrieval, transactions, lock management, query processing, etc.), but it uses an object oriented model to store and manage data. You can easily store ordinary | |
ObjectDB 2.9 Developer's Guide how to use the JPA Query Language (JPQL). Presents ObjectDB Tools: the Explorer, the Enhancer, the Doctor | |
General Settings and Logging The configuration element specifies ObjectDB settings that are relevant to both the server and the client. The default configuration file contains the following element: The element To meet memory constraints, ObjectDB can use temporary files when processing large amounts of data, such as query | |
jakarta.persistence.criteria.CommonAbstractCriteria The CommonAbstractCriteria interface defines functionality that is common to both top-level criteria queries ... directly in query construction. Note that criteria queries and criteria update and delete operations are typed differently. Criteria queries are typed according to the query result type. Update | |
jakarta.persistence.Parameter of the parameter Type for query parameter objects. See Also: Query TypedQuery Since: Jakarta Persistence (JPA) 2.0 Chapter 4 - JPA Queries (JPQL / Criteria) explains how to use Parameter . Public Instance ... must be assignable to this type. This method is required to be supported for criteria queries | |
jakarta.persistence.criteria.ParameterExpression , TupleElement Type of criteria query parameter expressions. Since: Jakarta Persistence (JPA) 2.0 Public ... do not affect the query . Inherited from Selection Returns: list of selection items. Throws ... to this type. This method is required to be supported for criteria queries only. Applications that use | |
jakarta.persistence.criteria.Path.get(String) to avoid the use of Path variables . For example: CriteriaQuery q = cb.createQuery(Person.class); Root | |
jakarta.persistence.FlushModeType Enumerates flush modes recognized by the EntityManager . When queries are executed within a transaction, if AUTO is set on the Query or TypedQuery object, or if the flush mode setting for the persistence context is AUTO (the default) and a flush mode setting has not been specified for the Query or | |
Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct), the inability to robustly query relationship fields in a web application renders the ObjectDB ... showing the query result in indexTest.xhtml. The problems is illustrated by running the attached JavaEE ... . For a number of different List fields, a query performed immediately after creating and persisting | |
jakarta.persistence.criteria.CriteriaQuery.multiselect(Selection...) in the query result. Replaces the previously specified selection(s), if any. The type of the result of the query execution depends on the specification of the type of the criteria query object ... : If the type of the criteria query is CriteriaQuery (i.e., a criteria query object created by | |
jakarta.persistence.criteria.CriteriaQuery.multiselect(List) the query result. Replaces the previously specified selection(s), if any. The type of the result of the query execution depends on the specification of the type of the criteria query object created as ... follows: If the type of the criteria query is CriteriaQuery (i.e., a criteria query object created | |
Unexpected Query Token / Casting in Query Hi! Please find the attached database. Doing a simple query with casting SELECT COUNT(DISTINCT $1 ... .IndividualContactDebitorAccountFragment')).debitorAccount.bankAccounts.routingNumber) LIKE UPPER('%28%') results in the error Query Execution Error ===================== Unexpected query token 'com.quasado.foundation.warehouse.api | |
jakarta.persistence.NamedStoredProcedureQuery sets is undefined. The hints element may be used to specify query properties and hints. Properties ... recognized by a provider must be ignored. All parameters of a named stored procedure query ... to the query with the EntityManager methods that create stored procedure query objects | |
jakarta.persistence.EntityManager.createNamedQuery(String,Class) for executing a Jakarta Persistence query language named query . The select list of the query must contain ... . Parameters: name - the name of a query defined in metadata resultClass - the type of the query result Returns: the new query instance. Throws: IllegalArgumentException - if a query has not been defined | |
Query on primary key is slow when using 'IN'); } } } We have about 200M instances of this entity. The following query finishes instantly: SELECT FROM ... = '1344770') Query plan 1/2 description ============================ [Step 1] Scan type eu.extech ... equalities to IN, the query suddenly takes 2.5 minutes: SELECT FROM ProductVariantStoreData d WHERE d | |
Issue with DISTINCT Select are used for both: Explicit variables in criteria queries . Implicit variables that are generated as ... of a criteria query , so probably $3 in this case is an implicit variable . Invalid order expressions is a common ... selection in our code (no changes else) and suddenly receive invalid identifiers in queries exceptions | |
jakarta.persistence.EntityManager.createNamedQuery(String) Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager Query createNamedQuery ( String name ) Create an instance of Query for executing a named query written in the Jakarta Persistence query language or in native SQL. Parameters: name - the name of a query defined in | |
jakarta.persistence.ColumnResult ConstructorResult annotation to map a column of the SELECT list of a SQL query . The name element references ... can be included in the query result by specifying this annotation in the metadata. Example: Query q = em ... name (Required) The name of a column in the SELECT clause of a SQL query Since: Jakarta Persistence | |
jakarta.persistence.EntityResult the SELECT clause of a SQL query to an entity result. If this annotation is used, the SQL statement ... . Example: Query q = em.createNativeQuery( "SELECT o.id, o.quantity, o.item, " + "i.id, i.name, i ... by the SQL query . Default: LockModeType.OPTIMISTIC Since: Jakarta Persistence (JPA) 3.2 FieldResult | |
jakarta.persistence.TypedQueryReference: - an upper bound on the result type of the query A reference to a named query declared via the NamedQuery ... .0 String getName () The name of the query . Since: Jakarta Persistence (JPA) 1.0 Class getResultType () The result type of the query . Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.Tuple the elements of a query result tuple. See Also: TupleElement Since: Jakarta Persistence (JPA) 2.0 Public ... - if tuple element does not correspond to an element in the query result tuple. Since: Jakarta ... does not correspond to an element in the query result tuple or element cannot be assigned | |
jakarta.persistence.SqlResultSetMapping query or stored procedure. Example: Query q = em.createNativeQuery( "SELECT o.id AS order_id, " + "o ... = "item_name") }) See Also: Query StoredProcedureQuery NamedNativeQuery NamedStoredProcedureQuery ... mapping, and used to refer to it in the methods of the Query and StoredProcedureQuery APIs | |
jakarta.persistence.NamedQueries Jakarta Persistence (JPA) Annotation Type jakarta.persistence.NamedQueries Implemented Interfaces: Annotation Target: Type Declares multiple named Jakarta Persistence query language queries . Query ... mapped superclass. See Also: NamedQuery Since: Jakarta Persistence (JPA) 1.0 The JPA Named Queries | |
InternalException when using MEMBER OF on a large list in a query Hello, we get when executing a query with MEMBER OF on a large list the following ... .o.PBI.q(PBI.jave:97) at com.objectdb.o.OBI.Vp(OBI.java:244) (... more see attached Image) Our query ... propertyClassName = propertyClass.getName(); String query = "SELECT DISTINCT property.uid FROM | |
Slow query due to scanning multiple indexes make a query for only one field, it takes 0-3 milliseconds: SELECT p FROM RackPlanogram p WHERE p.rackOID = "826268" Query plan 1/2 description ============================ [Step 1] Scan index eu.extech ... '*:notNull]) / However, when I make a query for two fields, ObjectDB does a scan |