About step by step

191-200 of 200Refresh
Forum
2

Schema Evolution Question

the following steps: Stop old client application. Stop ObjectDB. Start ObjectDB. Start NEW client ... Thank you!   The correct steps are: Stop old client application with the old schema. Stop ObjectDB server. Start ObjectDB server. Start new client application with the new schema. I followed these steps
Forum
2

How to deploy an Objectdb project with Jboss AS 7?

. Is there an instruction how to deploy objectdb project to Jboss AS 7 step by step?   I used objectdb ... .Thread.run(Thread.java:722) [rt.jar:1.7.0_21] Caused by: javax.persistence.PersistenceException ... : Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671
Result
2

Eclipse Public License - v 1.0

additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or ... entity that distributes the Program. "Licensed Patents" mean patent claims licensable by
Manual
2

JPA / JDO Class Enhancer

ObjectDB Enhancer is a post compilation tool that improves performance by modifying the byte code ... (and actually required by JPA but not enforced by ObjectDB) to avoid accessing persistent fields ... . by using the get and set methods). If you follow this practice only user defined persistable
Manual
2

JPA Persistable Types

are represented in queries by entity names. By default, the entity name is the unqualified name ... explicitly by using the name attribute of the Entity annotation: @Entity(name="MyName") public ... superclasses are treated by ObjectDB as ordinary entity classes. Mapped superclasses are really
Forum
2

Eclipse plugin problem (using ObjectDB as a separate bundle)

the problem I cleaned by project, and enhanced with ObjectDB with the small utility class public class ... cascaded automatically to referenced objects by default. Therefore, when you persist an object it must reference only objects that are already managed by ObjectDB - otherwise you get this exception
Result
2

ObjectDB Object Database Features [2018-01-27]

Databases are also supported by ObjectDB. The combination of Object Database features ... . Up to 9,223,372,036,854,775,808 entity objects per database file. Unlimited database connections (limited only by operating system resources). Unlimited CPUs and cores. Reliability and Stability Recovery from failure by
Result
2

ObjectDB Object Database Features [2018-10-27]

Databases are also supported by ObjectDB. The combination of Object Database features ... . Up to 9,223,372,036,854,775,808 entity objects per database file. Unlimited database connections (limited only by operating system resources). Unlimited CPUs and cores. Reliability and Stability Recovery from failure by
Result
2

ObjectDB Object Database Features

Databases are also supported by ObjectDB. The combination of Object Database features ... objects per database file. Unlimited database connections (limited only by operating system resources). Unlimited CPUs and cores. Reliability and Stability Recovery from failure by using a recovery file
Forum
2

JPQL query to get entities that does not have a child entity in their child entities

:12:10 14:00:00      001 02    Step_1_Started        2105:12:10 14:00:00      001 03    Step_1_Finished       2105:12:10 14:00:05      001 04    Step_2_Started        2105:12:10 14:00:05      001 05    Step_2_Finished       2105:12:10 14:00:10      001 06    Finished              2105:12:10 14:00