Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.
Internal Website Search1-10 of 200 resultsRefresh
Fields of persistable user defined classes (entity classes, embeddable classes and mapped superclasses) can be classified into the following five groups: Transient fields Persistent fields Inverse (Mapped By) fields Primary key (ID) fields Version field The first three groups (transient, persistent
The way a field of a persistable class is managed by JPA can be set by the following annotations: Additional annotations (and enum) are designated for enum fields: Other additional annotations (and enum) are designated for date and calendar fields: Chapter 2 of the ObjectDB manual explains how to use all the above annotations.
Modifications to entity classes that do not change their persistent field definitions (their schema ... and non persistent fields. However, additions, deletions and modifications to the persistent fields ... again. Conversion of an entity object to the new schema is done on a field by field basis: For every field in
The <schema> configuration element supports renaming packages, classes and fields in ObjectDB ... " /> <class name="B"> <field name="f1" new-name="newF1" /> <field name="f2" new-name="newF2 ... ="NewC" > <field name="f3" new-name="newF3" /> </class> <class name="C$E" new-name="NewC
Explains how to define and use JPA entity classes and other JPA persistable types.
The way a field of a persistable class is managed by JDO can be set by the following annotations and enum types:
declaring a persistent class as a subclass of a non persistent class. Of course, in that case the fields of class X are not persistent fields, and when an instance of class C is stored, only persistent fields ... always uses datastore identity with its own object-id class). 4.3 Metadata for Fields Unlike
Static Field javax.jdo.FetchPlan int DETACH_UNLOAD_FIELDS For use with PersistenceManager.detachCopy and setDetachmentOptions. Specifies that fields that are loaded but not in the current fetch plan should be unloaded prior to detachment. Since: JDO 2.0
Static Field javax.jdo.FetchPlan int DETACH_LOAD_FIELDS For use with PersistenceManager.detachCopy and setDetachmentOptions. Specifies that fields that are not loaded but are in the current fetch plan should be loaded prior to detachment. Since: JDO 2.0
Method javax.jdo.spi.StateManager void setStringField( PersistenceCapable pc, int field, String currentValue, String newValue ) Mark the field as modified by the user. Parameters: pc - the calling PersistenceCapable instance field - the field number currentValue - the current value of the field