ObjectDB Database Search
1-50 of 200 resultsjakarta.persistence.criteria.CriteriaBuilder.not(Expression) Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.CriteriaBuilder Predicate not ( Expression restriction ) Create a negation of the given restriction. Parameters: restriction - restriction expression Returns: not predicate. Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.criteria.Predicate.not() Jakarta Persistence (JPA) Method in jakarta.persistence.criteria.Predicate Predicate not () Create a negation of the predicate. Returns: negated predicate. Since: Jakarta Persistence (JPA) 1.0 | |
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 ... on update side does not any diference. The problem is only solved when changing the query mode, from ... that updates by queries bypass the cache and may result in not being seen by queries : "Updating | |
Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found through @Inject. Both are not entities or anything related to ObjectDB. AuthB is used in a JSF page for login ... enhancement. As you noted, this class is not related to ObjectDB and does not need enhancement | |
NOT NULL not working I added a OneToOne Realtionship to one of my entity classes. To give this field a value in my existing datasets i wrote an upgrade method. The cool thing is that SELECT u FROM Unit u WHERE u.lastPosition IS NOT NULL returns no datasets. Is this a bug or am i missing something? mosi0815 Ralph | |
Retrieving JPA Entities objects does not require an active transaction because it does not change the database content. The persistence context serves as a cache for retrieved entities. If a requested entity is not in ... object with a primary key of 1: Employee employee = em. find (Employee.class, 1); You do not need | |
Collections in JPQL and Criteria Queries is passed as an argument. As path expressions when navigating to a persistent collection field. IS [ NOT ] EMPTY The IS [ NOT ] EMPTY operator checks whether a specified collection is empty. For example: c ... IS NOT EMPTY evaluates to TRUE if the collection is not empty and FALSE otherwise. SIZE The SIZE | |
JPA Persistable Types: Must be a top-level class (that is, not a nested or inner class). Must have a public or protected no-argument constructor. Must not be final and must not have final methods or final instance variables ... classes are not . Instance (non-static) variables cannot be `final`, but classes and methods | |
Logical Operators in JPQL and Criteria API the following table: Set 1: JPQL / SQL Set 2: Java / JDO AND && OR || NOT ! JPQL uses SQL notation ... , ObjectDB also supports the Java/JDO || operator as a synonym for OR . Unary NOT (!) operator The following query retrieves all countries whose population does not exceed a specified limit: SELECT c FROM | |
Eclipse Public License - v 1.0 anyone acting on such Contributor's behalf. Contributions do not include additions to the Program ... under their own license agreement, and (ii) are not derivative works of the Program. "Contributor" means any person or ... to be covered by the Licensed Patents. The patent license shall not apply to any other combinations | |
Apache License, Version 2.0, January 2004. "Source" form shall mean the preferred form for making modifications, including but not limited ... resulting from mechanical transformation or translation of a Source form, including but not limited ... . For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely | |
ObjectDB License Agreement [ver. 2.0.4] the software you agree to the terms and conditions of this agreement. If you do not agree to these terms and conditions - do not download, install or use the software. This agreement is between ObjectDB ... of this agreement. 2. The Customer is not allowed to modify the Software or any portion of it in any | |
Detached JPA Entities Detached entities are objects in a special state where they are not managed by an EntityManager ... have limited functionality: Many JPA methods, for example, lock , do not accept detached objects. Retrieval by navigation from detached objects is not supported. You can only access persistent fields | |
jakarta.persistence.EntityManager one of the following lifecycle states: A new entity has no persistent identity, and is not ... identity that is not (or no longer) associated with any active persistence context. A removed ... are not immediately synchronized with the database. Synchronization happens during a process called | |
FROM clause (JPQL / Criteria API). The WHERE clause filters any pair of countries that do not share a border, returning only neighboring ... a simpler, long path expression (which is not an option for a collection). For example: SELECT c, c.capital ... ) pairs. A country with no capital city (for example, Nauru, which does not have an official capital | |
JPA Shared (L2) Entity Cache that the EntityManager already manages returns the existing instance from the persistence context, not a newly ... classes except those explicitly marked as not cacheable . For example: @Cacheable (false) @Entity ... is an inherited annotation. An entity class that is not marked with @Cacheable inherits the cacheability setting | |
ObjectDB Website - Terms and Conditions of Use for compliance with any applicable local laws. If you do not agree with any of these terms, you are prohibited ... -commercial transitory viewing only. This is the grant of a license, not a transfer of title, and under this license you may not : modify or copy the materials; use the materials for any commercial | |
SELECT clause (JPQL / Criteria API) for deletion , and so on. Query results are not limited to entities. You can use almost any valid JPQL ... must always be specified explicitly. JPQL does not support the the SELECT * expression, which is common in SQL. Projection of path expressions JPQL queries can also return results that are not entities. For example | |
JPA Query Expressions (JPQL / Criteria) : = , , = , IS [ NOT ] NULL , [ NOT ] BETWEEN Collection operators: [ NOT ] IN , IS [ NOT ] EMPTY , [ NOT ] MEMBER [OF] String operator : [ NOT ] LIKE Logical operators : AND , OR , and NOT JPA queries also support predefined ... , between , isNull , …) Logical expressions ( and , or , not , isTrue ) | |
Privacy Policy information may include, but is not limited to: email address, username, full name, user name, profile ... automatically, including, but not limited to, the type of mobile device You use, Your mobile device unique ID ... is being sent. However, if You do not accept Cookies, You may not be able to use some parts | |
Comparison in JPQL and Criteria API/SQL Set 2: Java/JDO Less Than Less Than or Equal To = Equal To = == Not Equal To != The main difference between the two sets is the syntax for the equal to ( = vs. == ) and not equal to ( vs ... Comparison operators always evaluate to TRUE , FALSE , or NULL . When neither operand is NULL (a case not | |
JPA Entity Fields transient1; // not persistent because of static final int transient2 = 0; // not persistent because of final transient int transient3; // not persistent because of transient @Transient int transient4; // not persistent because of @Transient } The preceding entity class contains only transient (non | |
Strings in JPQL and Criteria Queries. LIKE - string pattern matching with wildcards The [ NOT ] LIKE operator checks whether a string ... (for any c.name value). c.name NOT LIKE '%' is always FALSE (for any c.name value). To match a literal ... ', 'a') is evaluated to 0 . Positions are one-based (as in SQL), not zero-based (as in Java | |
JPA Primary Key, ObjectDB supports implicit object IDs, so an explicit primary key is not required. However, ObjectDB ... part of their containing entities and do not have a separate identity. Automatic primary key By default ... are not recycled when entities are deleted from the database. You can access an entity's primary key | |
JPA Class Enhancer of enhanced classes ( not through methods) must also be enhanced. It is a good practice to avoid ... but not enforced by ObjectDB. Instead, use the accessor and mutator methods of the desired class ... classes require enhancement. The enhancer silently ignores any specified class that does not need | |
Literals in JPQL and Criteria Queries ) numeric literals. This feature is not supported by all JPA implementations. String literals JPQL ... escape characters (for example, "Adam\'s" and "abcd 1234" ). However, this syntax is not supported by ... ) are case-sensitive, so 'abc' and 'ABC' are not equivalent. Date and time literals JPQL follows | |
Database Management Settings a database and finds a recovery file, which indicates that the database was not closed properly. Moving or copying a database file that was not closed properly without its recovery file might corrupt ... to automatically repair a database that was not closed properly by running the Replayer tool | |
Query Parameters in JPA does not provide an API to define parameters explicitly (except when using the Criteria API). Instead ... for all its parameters. The order in which you set the parameters does not matter. Ordinal ... has several drawbacks. First, the query is not reusable. Different literal values result in different query | |
Database Explorer line as follows: $ java -jar explorer.jar If explorer.jar is not in the current directory ... Object... to set a reference to a new object, which does not have to be an entity. Field values ... . If you delete a reference field, its value is set to null , and the referenced entity is not deleted | |
jakarta.persistence.StoredProcedureQuery of all required IN and INOUT parameters. It is not required to set the values of stored procedure ... is not an update count. The provider will call execute on the query if needed. Overrides Query.executeUpdate Returns: the update count or -1 if there is no pending result or if the next result is not | |
JPA Core Types, and managing the persistence context. Because it is not thread-safe, you should use a separate instance ... environments that do not use JTA. Use this interface to explicitly begin , commit , or roll ... attributes, and access entity content not yet fetched due to lazy loading. Provides an API for programmatic | |
Database Schema Evolution Modifications to entity classes that do not change their persistent field definitions ... the new schema that do not have matching fields in the old schema are initialized with default values ( 0 , false , or null ). Fields in the old schema that do not have matching fields in the new schema | |
Deleting JPA Entities back, the object is not deleted. The remove method throws an IllegalArgumentException if its argument is not an entity instance or if it is a detached entity. It throws a TransactionRequiredException ... ) that should not exist without a reference from an owner object (such as Employee ). If only cascade | |
JPA Metamodel API allEmbeddableTypes = metamodel. getEmbeddables (); If managed classes are not listed in the persistence unit ... . embeddable (MyEmbeddableType.class); You can also use these three methods with types that are not yet known to ObjectDB (for example, types that are not listed in the persistence unit and have not | |
Updating JPA Entities that are not yet managed are also persisted. Automatic change tracking As shown previously, you update an entity by modifying it within an active transaction. You do not need to invoke an EntityManager method ... (). begin (); employee.projects[0] = new Project(); // not detected automatically JDOHelper . makeDirty | |
jakarta.persistence.TypedQuery the persistence context has not been joined to the transaction. QueryTimeoutException - if the statement ... result the query object was set to retrieve. Returns 0 if setFirstResult was not applied to the query ... () Get the flush mode in effect for the query execution. If a flush mode has not been set | |
jakarta.persistence.Query - if there is no transaction or the persistence context has not been joined to the transaction. QueryTimeoutException ... was set to retrieve. Returns 0 if setFirstResult was not applied to the query object. Returns ... for the query execution. If a flush mode has not been set for the query object, returns the flush mode in | |
Storing JPA Entities is committed. The persist method throws an IllegalArgumentException if the argument is not an entity ... , the referenced Address instance is not automatically stored in the database with the referencing Employee ... if a persisted entity references another entity that is not stored in the database at the end | |
Schema Update configuration file contains an empty element. If this element is not empty, ObjectDB tries to apply ... .example.old3 package is not renamed, but rename operations are specified for some of its classes ... , and C.E (written as C$E ) classes. Class B is not renamed but rename operations are specified | |
Is ObjectDB better than competing object databases? Naturally, this is not the place to look for an unbiased answer for this question ... , most object databases do not support user defined primary keys, even though this is very useful in ... do not support aggregate queries (max, min, count, sum and avg). ObjectDB supports rich queries | |
Index Definition indexes only on ordinary persistent fields, not on primary key or version fields. Composite index ... is an ordered map data structure that ObjectDB maintains in the file system, not in memory. The B ... is sorted lexicographically by word, not by word length. In summary, if an index contains all the fields in | |
Auto Generated Values. This generator creates automatic object IDs for entities that do not have defined primary key ... might not be used. Therefore, this strategy can result in gaps in the sequence values.nd The Table ... this strategy. ObjectDB does not have tables, so the TABLE and SEQUENCE strategies are almost identical | |
Defining a JPA Entity Class classes When you store an entity in the database, its methods and code are not stored ... field that is not declared as static or transient is a persistent field. For example, the persistent ... an object database, ObjectDB supports implicit object IDs, so an explicit primary key is not required | |
UPDATE SET Queries in JPA/JPQL, the EntityManager might not be aware that an UPDATE query has modified a cached entity in ... without an explicit variable name) for iteration. Multiple variables and JOIN operations are not supported ... . However, they do not support the GROUP BY , HAVING , and ORDER BY clauses. For example, the following | |
Paths and Types in JPQL and Criteria API is not Country are passed to the SELECT clause. The SELECT clause then counts all these objects ... not affect the query directly. The constructed expression must be explicitly integrated into ... if the type of a specified entity e is not Country . Predicate p = cb. notEqual (e. type (), cb. literal | |
GROUP BY and HAVING clauses might not be supported by other JPA implementations. Currently, only identification variables and path ... . For example, the preceding query, which does not use aggregates, is equivalent to the following query ... of aggregate query that does not have a GROUP BY clause. In these queries, all objects or tuples | |
Managing JPA Entities. When an entity is first created, its state is New . In this state, the object is not yet associated ... and other caches, as explained in the Configuration chapter. By default, managed entities that have not ... , all of its managed entities become detached, and any changes to entities that have not | |
Collection update does not increase entity version and is not persisted { String filename } If I call this method (all classes are enhanced) the version of the event does not increase and the updated event is not stored in the database (retrieve the event shows ... an attachment via addAttachment() method and checks in another transaction if this change was written or not | |
"is not null" queries not working with index "is not null"-queries are not working correctly for indexed fields. Following SSCCE creates 1000 entities. A null value is assigned to an indexed field for every second entity. When doing count-queries at the end, wrong results are fetched. import java.io.Serializable; import javax.jdo.annotations | |
jakarta.persistence.criteria.CriteriaBuilder is used instead of Expression in this API in order to work around the fact that Java generics are not ... ) Create a predicate that tests whether a collection is not empty. Parameters: collection - expression Returns: is- not -empty predicate. Since: Jakarta Persistence (JPA) 1.0 Predicate isNotMember |