ObjectDB Database Search
1-50 of 200 resultsCan't modify @EmbeddedId in ObjectDB Explorer Hi! There is entity Journal with @EmbeddedId JournalId. Id's content can't be seen/ modified from ... only on its parent. Problem: id's content can't be modified through its parent neither. Scenario: open db in ObjectDB Explorer, open entity Journal, expand the id, try to modify date/id, save, then refresh data | |
Modifying something with Explorer -> app JPQL with Enum doesn't work anymore is printed in the console, open ObjectDB Explorer, modify an entity's type from GOOD to BAD, save ... the problem, which says the problem also. Repeat case 1 but don't modify anything. Just open and close the DB in Explorer. (Follow all the steps, but don't modify .) Just by doing | |
2.7.3_03 Erroneous "Attempt to modify a primary key of a managed object" ObjectDB 2.7.3_03 gives my application a "com.objectdb.o.UserException: Attempt to modify ... The exception should be thrown on an attempt to modify a primary key of a managed object. Older ... , the error I got was the same as the title of this thread: Erroneous "Attempt to modify a primary | |
Conflicting modifiers .... (javax.persistence.Id, javax.persistence.ManyToOne) Creating Database [ObjectDB 2.2.9_05] javax.persistence.PersistenceException Conflicting modifiers ... .UserException: Conflicting modifiers for field uk.co.his.experiment8.cmdline.objdb.CompoundKeyMapItem | |
Remove a modified entity cause an optimistic lock exception Hello, the following examples load and modify an entity, and load and remove the same entity. The first example 'SetAndRemoveIssue.java' is a simple java program which executes without errors ... BTC EmbeddedSystems The OSGi test is based on: Retrieving an object from the database. Modifying | |
Support of modifying an ObjectDB Entity class (Schema Change) If you modify an ObjectDB Entity class will it be supported by a database set up using the old class? I already have an idea to iterate through a database, getting each record and then creating a record of the new type and replacing it, but I was just wondering if there is an easier way or | |
Modifier operations Hi, Today I was reading about different NoSQL databases. One of those database - MongoDB - has a very nice feature, especially for web applications - modifier operations. The whole trick for those operations is to change some value in object without pulling this object from database | |
Updating JPA Entities Modifying existing entities in the database relies on transparent persistence, which automatically ... , you can modify it in memory within an active transaction: Employee employee = em. find (Employee.class ... all entities that need to be stored, including all modified entities. Therefore, entities | |
Apache License, Version 2.0, January 2004; and You must cause any modified files to carry prominent notices stating that You changed the files ... are for informational purposes only and do not modify the License. You may add Your own attribution notices ... the Work, provided that such additional attribution notices cannot be construed as modifying the License | |
JPA Connections and Transactions. Once constructed, it can serve the entire application. Operations that modify the database require active ... "); EntityManager em = emf. createEntityManager (properties); EntityTransaction Operations that modify ... { em. getTransaction (). begin (); // Operations that modify the database should come here. em | |
UPDATE SET Queries in JPA/JPQL an alternative way to update entities. Unlike SELECT queries, which retrieve data, UPDATE queries modify ... , the EntityManager might not be aware that an UPDATE query has modified a cached entity in ... queries The simplest form of an UPDATE query modifies all instances of a specified entity class in | |
JPA Optimistic and Pessimistic Locking after the current transaction retrieved it, so the current transaction is attempting to modify a stale version ... ;is modified , its version number is automatically incremented by one. Version numbers are managed internally ... that another user (using another EntityManager ) has modified the object since the current transaction | |
Obtaining a JPA Database Connection. Therefore, to manipulate an ObjectDB database, you need an EntityManager instance. Operations that modify database ... that modify database content, such as storing, updating, and deleting entities, must be performed ... , you can invoke EntityManager methods that modify the database content, such as persist and remove | |
Server User List can contain the following permissions: access : Permission to open a database for reading. modify : Permission to modify the contents of a database. create : Permission to create new subdirectories ... database files or modify anything. The element Each element can contain an optional subelement | |
JPA Entity Fields either the Java transient modifier (which also affects serialization) or the JPA @Transient ... that modifies an entity, its version number is automatically incremented by one. Version fields are used | |
JPA Persistable Types. It can contain constructors, methods, fields, and nested types with any access modifier ( public , protected ... , enum values are represented internally by their ordinal numbers. Use caution when modifying an enum | |
JPA Class Enhancer The ObjectDB Enhancer is a post-compilation tool that improves performance by modifying the bytecode of compiled classes. Enhancement applies mainly to user-defined persistable classes ( entity ... whenever a persistent field is modified . Enhanced code enables lazy loading of entities | |
Eclipse Public License - v 1.0 the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward ... . No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse | |
Managing JPA Entities Entities section discusses object retrieval in more detail. If a managed entity is modified ... been modified or removed during a transaction are held in the persistence context by weak references | |
JPA Exceptions is required but is not active. This typically occurs when attempting to modify the database ... that another transaction modified the entity since it was last read. Thrown when a pessimistic lock | |
JPA Listeners & Callbacks Annotations when modifying existing entities and flushing changes to the database: Executes before the database update operation. This is typically used to update "last modified " timestamps or validate state changes | |
jakarta.persistence.criteria.CriteriaQuery must be eliminated from the query result or whether they must be retained Returns: the modified query ... AbstractQuery.groupBy Parameters: grouping - zero or more grouping expressions Returns: the modified ... expressions Returns: the modified query. Since: Jakarta Persistence (JPA) 1.0 CriteriaQuery having | |
jakarta.persistence.criteria.Subquery whether they must be retained Returns: the modified subquery.. Since: Jakarta Persistence (JPA) 1.0 Predicate equalTo ... Parameters: grouping - zero or more grouping expressions Returns: the modified subquery. Since: Jakarta ... : the modified subquery. Since: Jakarta Persistence (JPA) 1.0 Subquery having ( Expression restriction | |
jakarta.persistence.criteria.AbstractQuery the query result or whether they must be retained Returns: the modified query. Since: Jakarta ... . Parameters: grouping - zero or more grouping expressions Returns: the modified query ... removed. Parameters: grouping - list of zero or more grouping expressions Returns: the modified query | |
JPA Lifecycle Events when the EntityManager detects that an entity has been modified . @PostUpdate : Invoked after an entity | |
Database Management Settings, which modify the database. For debugging query failures, you might need to record "all" operations to reproduce | |
Storing JPA Entities entities. Because operations that modify the database require an active transaction, persist throws | |
ObjectDB License Agreement [ver. 2.0.4] of this agreement. 2. The Customer is not allowed to modify the Software or any portion of it in any | |
Detached JPA Entities a TransactionRequiredException if you call it without an active transaction, because merging can modify | |
DELETE Queries in JPA/JPQL is a good practice. As with any operation that modifies the database, DELETE queries must be executed | |
How to install ObjectDB? ObjectDB is distributed as a zip file. Just download and extract the ObjectDB distribution zip file. No need to run any install or setup program. You can uninstall ObjectDB by deleting the ObjectDB directory. ObjectDB does not modify the registry or any other system file. | |
Database Doctor. Modifying the database file externally instead of through ObjectDB (for example, with malicious software | |
Database Schema Evolution Modifications to entity classes that do not change their persistent field definitions (their schema) are transparent to ObjectDB. This includes adding, removing, or modifying constructors, methods, and non-persistent fields. However, ObjectDB detects additions, deletions, and modifications | |
What's next? program. You can start your own ObjectDB/JPA projects by modifying this example program | |
JPA Shared (L2) Entity Cache and then added to the shared cache. On commit : New and modified entities are added to the shared cache | |
Entity Management Settings. The valid values are "weak" , "soft" , and "strong" . Modified entities are always held by strong | |
Paths and Types in JPQL and Criteria API modifies the query by adding a variable to the FROM clause, which represents iteration during query | |
GROUP BY and HAVING clauses is only supported when a GROUP BY clause is also present. The following query modifies the previous query by using | |
ObjectDB Website - Terms and Conditions of Use, and under this license you may not: modify or copy the materials; use the materials for any commercial | |
Database Explorer in client-server mode, other applications can access it simultaneously. If another process modifies | |
JPA Primary Key Every entity stored in the database has a primary key. Once assigned, the primary key cannot be modified and represents the entity for as long as it exists in the database. As an object database, ObjectDB supports implicit object IDs, so an explicit primary key is not required. However, ObjectDB | |
jakarta.persistence.criteria.CriteriaUpdate: the modified update query. Since: Jakarta Persistence (JPA) 1.0 CriteriaUpdate set ... - attribute to be updated value - new value Returns: the modified update query. Since: Jakarta ... attribute. Parameters: attribute - attribute to be updated value - new value Returns: the modified | |
jakarta.persistence.LockModeType phenomena can occur: P1 (Dirty read): Transaction T1 modifies a row. Another transaction T2 then reads that row and obtains the modified value, before T1 has committed or rolled back. Transaction T2 ... T2 then modifies or deletes that row, before T1 has committed. Both transactions eventually commit | |
jakarta.persistence.criteria.PluralJoin Persistence (JPA) 3.2 Join on ( Expression restriction ) Modify the join to restrict the result ... : the modified join object. Since: Jakarta Persistence (JPA) 2.1 Join on ( Predicate... restrictions ) Modify the join to restrict the result according to the specified ON condition and return the join | |
jakarta.persistence.criteria.MapJoin (JPA) 3.2 MapJoin on ( Expression restriction ) Modify the join to restrict the result according ... : the modified join object. Since: Jakarta Persistence (JPA) 2.1 MapJoin on ( Predicate... restrictions ) Modify the join to restrict the result according to the specified ON condition and return the join object | |
jakarta.persistence.criteria.SetJoin restriction ) Modify the join to restrict the result according to the specified ON condition and return ... - a simple or compound boolean expression Returns: the modified join object. Since: Jakarta Persistence (JPA) 2.1 SetJoin on ( Predicate... restrictions ) Modify the join to restrict the result according | |
Step 3: Define an EJB Session Bean JTA - no need to wrap every operation that modifies the database (such as persist ) by | |
Step 3: Define a Spring DAO Component, saving the need to wrap every operation that modifies the database (such as persist ) by transaction | |
Step 3: Define a Spring DAO Component the need to wrap every operation that modifies the database (such as persist ) by transaction begin | |
Step 3: Define an EJB Session Bean - no need to wrap every operation that modifies the database (such as persist ) by transaction begin |