ObjectDB Database Search
101-150 of 200 resultsJPA 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 | |
query on calendar class Hello! I'm looking for help to build query on calendar class. I need to get objects ... ; @Temporal(TemporalType.TIMESTAMP) private Calendar start; I tested: Query query =em.createQuery("SELECT c FROM Cdr c where c.start.DAY_OF_WEEK = ?1",Cdr.class); query .setParameter(1,Calendar.FRIDAY | |
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 | |
how to query by properties of onetomany relations? (Error 990) - it should be replaced by a more descriptive error message in future versions. However, this query ... a variable that will iterate over the collection elements. This specific query should be rewritten ... sql joins :) in my last projects i have been using mongodb and such a query was possible for embedded | |
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 | |
possible index required for improving query performance; } With the following query : TypedQuery 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 a linear way | |
JPA query of a Set of terms Hi, Is it possible to write a JPA query to select objects that contain a collection of elements ... WHERE si.term ????",Page.class); I want the query to give me all Pages that match all of the search ... that are already persisted. TypedQuery query = em.createQuery( "SELECT DISTINCT si.page FROM SearchIndex si | |
Query filter comparing Dates in query filters comparing this Date field. Could You please clarify why are there zero-size result collections in the first pack of queries and non-zero size results in the second pack ? I ... (); // these queries should find 1 item assertQueryResultSize(0, pm.newQuery(ClassWithDate.class | |
Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x, with object 1.x, the same query was getting executed within an seconds and now the same is taking around 40 seconds in object db 2.x I have build the query using the follwoing Query query = persistanceManager ... (this.logEntryId)"); query .declareParameters("java.util.List typeIndexes,java.util.List | |
Help with 'not like/lower' query Hi 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 | |
Optimization of Map Queries.get(..) result(s) once to not query the map again and again for each test in my query ? 2) Is there anything I could do for shortening the query string? I guess there's no such thing as a "temporary" variable for being used in the query .. I am creating the query using criteriabuilder, then I am converting | |
Performance issue in a query due to compareTo calls Hello, we have a question again regarding query performance. The query : SELECT v FROM Values v WHERE v.step.stepNumber = ? is very slow in comparing to the query : SELECT v FROM Values v WHERE v.stepNumber = ? Can you explain why the first query needs so much time or do you have a hint | |
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 ... query needs 4 to 5 minutes to return a result. I have been adviced to use indexes ... transient LogEntryImpl logEntryImpl; ... And I use such query : Query query = pm.newQuery(MessageImpl | |
Duplicate Entity class names causes Exception in Query of one of these entities. If I execute that query I get an exception; Caused by: com.objectdb.o ... the query on objdbTest.Item package objdbTest; import .... @Entity @NamedQueries({ @NamedQuery(name = "objdbTest.Singleton.getItem", query = "SELECT o FROM Item o WHERE o.cachedKey = :cachedKey | |
JPA Persistence Unit classes. However, it might be useful to register classes that define generators and named queries (by annotations). Otherwise, the generators and named queries are available only when the containing | |
ObjectDB Overview all the standard database management services (storage and retrieval, transactions, lock management, query ... file. Advanced querying and indexing capabilities. Effective in heavy loaded multi-user environments | |
InterfaceRef jakarta.persistence.StoredProcedureQuery JPA Interface StoredProcedureQuery Super Interfaces: Query Interface used to control stored procedure query execution. Stored procedure query execution may be controlled in accordance ... on a StoredProcedureQuery object, the provider calls execute on an unexecuted stored procedure query before | |
InterfaceRef jakarta.persistence.TypedQuery JPA Interface TypedQuery Type Parameters: - query result type Super Interfaces: Query Interface used to control the execution of typed queries . See Also: Query Parameter Since: JPA 2.0 Chapter 4 - JPA Queries (JPQL / Criteria) explains how to use TypedQuery . Public Methods int executeUpdate | |
JPA Lifecycle Events lifecycle event (which is still in progress) callback methods should not call EntityManager or Query | |
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 | |
JPA Metamodel API in the above sets extend the Bindable interface, which may be used in defining criteria query | |
ObjectDB 2.9 Developer's Guide how to use the JPA Query Language (JPQL). Presents ObjectDB Tools: the Explorer, the Enhancer, the Doctor | |
JPA Annotations for Relationships (which is calculated by a query ) : Details about all these annotations are provided in Chapter 2 of the ObjectDB manual. | |
JPA Annotations between a relational database and an object model and for direct SQL queries ): These ORM annotations are silently ignored by ObjectDB. | |
General Settings and Logging, such as query results that contain millions of objects. The element specifies temporary file settings | |
JPA Exceptions, when a required entity object is not found: or during query execution: The lock exceptions | |
InterfaceRef jakarta.persistence.EntityManager context must also be flushed before execution of any query whose result set would be affected by ... LockOption s. See Also: Query TypedQuery CriteriaQuery PersistenceContext StoredProcedureQuery ... and of any instance of Query , TypedQuery , or StoredProcedureQuery obtained from it throws | |
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 | |
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 | |
InterfaceRef jakarta.persistence.criteria.CriteriaQuery functionality that is specific to top-level queries . Since: JPA 2.0 The JPA Criteria API Queries article ... whether duplicate query results are eliminated. A true value will cause duplicates to be eliminated ... must be eliminated from the query result or whether they must be retained Return: the modified query . Since: JPA 2 | |
InterfaceRef jakarta.persistence.criteria.AbstractQuery queries and subqueries. It is not intended to be used directly in query construction. All queries must have: a set of root entities (which may in turn own joins). All queries may have: a conjunction ... whether duplicate query results are eliminated. A true value will cause duplicates to be eliminated | |
InterfaceRef jakarta.persistence.criteria.CriteriaBuilder JPA Interface CriteriaBuilder Used to construct criteria queries , compound selections, expressions ... Criteria API Queries article explains how to use CriteriaBuilder . Public Methods Expression abs ... to a constructor. This method is used to specify a constructor that is applied to the results of the query | |
queries under 2.7.6_4 significantly slower than under 2.7.6 indicating deep query plan checks and an overall significant performance loss in all queries ... since version 2.7.6 that could possibly effect query execution. Could you please explain or post some of these logs that show deep query plan checks (and are new in 2.7.6_04)? In addition | |
InterfaceRef jakarta.persistence.criteria.Subquery a subquery collection join object correlated to a collection join object of the enclosing query . Parameters: parentCollection - join object of the containing query Return: subquery join Since: JPA 2.0 ... of the enclosing query . Parameters: parentJoin - join object of the containing query Return: subquery | |
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 | |
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 | |
ClassCastException thrown when running count query Hello! 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 Hello ... the query below it will crash with the exception in crash.txt. select p from Position p where p.unit | |
Large query parameter - out of memory file as it goes. It then loops through the data from the file and queries for the entity id based ... this should be sufficient as I only create/read one item of data at a time and am only querying for the id. After about 300 queries the test throws an out of memory exception so I assume the query data is being held | |
Unexpected exception when execute query without enhanced entities ObjectDB 2.8.7.b08 Our entities are not enhanced and we execute a query "select max(uid) from ... exception after execution of the query : Caused by: com.objectdb.o.UserException: Unexpected query token ... : Unexpected query token 'uid'. If the entities are enhanced then the query works without exception. btc | |
Different behavior for two equal queries Hi, I've got two equal queries though they behave differently: SELECT FROM com.quasado.foundation ... Here're also the execution plans from the explorer if that helps: First query (which works): Query Plan ... and prepare final results. Second query (which fails): Query Plan Description | |
Step 3: Define an EJB Session Bean); } // Retrieves all the guests: public List getAllGuests() { TypedQuery query = em.createQuery( "SELECT g FROM Guest g ORDER BY g.id", Guest.class); return query .getResultList(); } } The GuestDao session bean (EJB |