ObjectDB Database Search
1-45 of 45 resultsjakarta.persistence.OneToOne.targetEntity Jakarta Persistence (JPA) Method in jakarta.persistence. OneToOne Class targetEntity (Optional) The entity class that is the target of the association. Defaults to the type of the field or property that stores the association. Default: void/class Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.OneToOne.cascade Jakarta Persistence (JPA) Method in jakarta.persistence. OneToOne CascadeType[] cascade (Optional) The operations that must be cascaded to the target of the association. By default no operations are cascaded. Default: {} Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.OneToOne.fetch Jakarta Persistence (JPA) Method in jakarta.persistence. OneToOne FetchType fetch (Optional) Whether the association should be lazily loaded or must be eagerly fetched. The EAGER strategy is a requirement on the persistence provider runtime that the associated entity must be eagerly fetched | |
jakarta.persistence.OneToOne.optional Jakarta Persistence (JPA) Method in jakarta.persistence. OneToOne boolean optional (Optional) Whether the association is optional. If set to false then a non-null relationship must always exist. Default: true Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.OneToOne.mappedBy Jakarta Persistence (JPA) Method in jakarta.persistence. OneToOne String mappedBy (Optional) The field that owns the relationship. This element is only specified on the inverse (non-owning) side of the association. Default: "" Since: Jakarta Persistence (JPA) 1.0 | |
jakarta.persistence.OneToOne.orphanRemoval Jakarta Persistence (JPA) Method in jakarta.persistence. OneToOne boolean orphanRemoval (Optional) Whether to apply the remove operation to entities that have been removed from the relationship and to cascade the remove operation to those entities. Default: false Since: Jakarta Persistence (JPA) 2.0 | |
JPA Entity Fields: @ OneToOne , @ManyToOne : For references to entity types. @OneToMany , @ManyToMany : For collections and maps ... EntityWithFieldSettings { @Basic ( optional =false) Integer field1; @ OneToOne ( cascade = CascadeType ... inverse fields are also supported: @Entity public class Employee { @ OneToOne MedicalInsurance | |
@OneToOne query issue with OR and IS NULL; @ OneToOne (mappedBy = "other", cascade ... ; private int counter; @ OneToOne private | |
Detached JPA Entities, which can be a single entity or a collection of entities: @Entity class Employee { : @ OneToOne ( cascade ... a collection of entities: @Entity class Employee { : @ OneToOne ( cascade = CascadeType . MERGE ) private | |
Retrieving JPA Entities through the field. Specifying FetchType . LAZY in either the @ OneToOne or @ManyToOne annotation excludes ... Employee { : @ OneToOne ( cascade = CascadeType . REFRESH ) private Address address; : } In | |
Storing JPA Entities can reference multiple entities. @Entity class Employee { : @ OneToOne ( cascade = CascadeType . PERSIST | |
jakarta.persistence.JoinColumn public Set getOrders() { return orders; } See Also: ManyToOne OneToMany OneToOne JoinTable ... . If the join is for a OneToOne or ManyToOne mapping using a foreign key mapping strategy, the foreign key ... entity. If the join is for a ManyToMany mapping or for a OneToOne or bidirectional ManyToOne | |
jakarta.persistence.MapsId Jakarta Persistence (JPA) Annotation Type jakarta.persistence.MapsId Implemented Interfaces: Annotation Target: Method, Field Designates a ManyToOne or OneToOne relationship attribute that provides ... or OneToOne relationship declared by a dependent entity is annotated MapsId , an instance | |
jakarta.persistence.JoinColumn.name. If the join is for a OneToOne or ManyToOne mapping using a foreign key mapping strategy, the foreign key ... . If the join is for a ManyToMany mapping or for a OneToOne or bidirectional ManyToOne / OneToMany | |
jakarta.persistence.JoinTable ManyToOne , OneToOne , ManyToMany , or OneToMany . See Also: JoinColumn JoinColumns Since: Jakarta | |
jakarta.persistence.ManyToOne annotation. Alternatively, an optional OneToOne association is sometimes mapped to a join table | |
jakarta.persistence.FetchType ManyToMany OneToMany ManyToOne OneToOne Since: Jakarta Persistence (JPA) 1.0 Enum Constants EAGER Data | |
significant performance decrease public String objectName; @ OneToOne public ObjectType objectType; @Index public Integer state; public Map ... = new ArrayList (); @ OneToOne (fetch=FetchType.LAZY) public ObjectNode currentLocation; @ OneToOne ... ArrayList (); @ OneToOne (fetch=FetchType.LAZY) public ObjectNode linkedType; @OneToMany(fetch | |
Performance issue in a query due to compareTo calls) @ElementCollection private Map values = new HashMap (); @ OneToOne (fetch = FetchType.LAZY, cascade ... ; @ OneToOne (fetch = FetchType.EAGER) private TCStep step; //For performance reasons, we use a list ... (AccessType.FIELD) public class Values extends Identifiable { @ OneToOne (fetch = FetchType.EAGER) private | |
EntityManager.refresh takes a long time.REFRESH) private List comments = new ArrayList (); @ OneToOne (cascade = CascadeType.ALL) private SiteAuth ... ; @ OneToOne (cascade = {CascadeType.PERSIST}) private Image mainImage; @ OneToOne (cascade = {CascadeType | |
Mapped By Fetch is very Slow again :( ). Here is the test case : 1- Create 100 000 entities with for each 1 entity with @ OneToOne (mappedBy ... .persistence.Id; import javax.persistence. OneToOne ; @Entity public class MyEntity { @Id private String name ... = null; @ OneToOne (targetEntity = MyEntityChild.class, cascade = CascadeType.ALL,mappedBy | |
Multiple Collection Fields not update correctly to another entity and they both reciprocally do: EntityB: @ OneToOne (cascade = CascadeType.ALL) EntityA entityA; EntityA: @ OneToOne (cascade | |
Multi threading on DMOs by lazy loading It is possible to use lazy loading on fields of attached entities by several threads? Example: class EntityZ { @ OneToOne (fetch = FetchType.LAZY) EntityX fieldX; @ OneToOne (fetch = FetchType.LAZY) EntityY fieldY; @ElementCollection (fetch = FetchType.LAZY) List list; } We want to load the entity | |
General Performance Issues Illustrated with a Specific Method; import javax.persistence.ManyToOne; import javax.persistence. OneToOne ; import javax.persistence.Table ... = GenerationType.AUTO) private Long id; private static final long serialVersionUID = 1L; @Index @ OneToOne | |
Composite indexes ? #4. Are @Index field used also on relations? @ OneToOne , @ManyToOne? I don't want to start ... with and without such an index. 4. Are @Index field used also on relations? @ OneToOne , @ManyToOne | |
Problem with @Basic(fetch = FetchType.LAZY) with @ OneToOne (fetch = FetchType.LAZY, cascade = CascadeType.ALL) private LargeString description; @ OneToOne (fetch = FetchType.LAZY, cascade = CascadeType.ALL)   | |
Using of Second Level Cache MyEntity1 { @ OneToOne private MyEntity2 | |
Are indexes implicitly created for relationships? Do the following annotations @OneToMany @ManyToOne @ManyToMany @ OneToOne imply @Index ? Thanks, Carl FastModel Ben Schreiber Actually these annotations (except @ManyToMany ) should apply @Unique on the @One side. But ObjectDB doesn't apply these indexes automatically | |
Database(*.odb) file size on disk; import javax.persistence.Id; import javax.persistence. OneToOne ; import javax.persistence.Persistence | |
"Unexpected query expression" using CriteriaQuery FetchParent Interface.class); root.fetch("PersonData"); //@ OneToOne relationship criteriaQuery.select(root | |
openejb jpa jaas module String mailAddress; @ OneToOne private Settings settings; private String phoneNumber; @OneToMany | |
Accessiblity of attributes in entities in several OSGi-Bundles() { return name; } } @Entity class MessageImpl { @ OneToOne private ModelElementImpl e; @Basic private | |
Global way to set Lazy-loading fetch functionality for all the fields Hi, for cascading persist, I have 3 choices: - Either locally (@ OneToOne (cascade=CascadeType.PERSIST)) - Either at objectdb level ( ) - Either at JPA global level (orm.xml). For defining fetch policy, I know the local way to do it (@ManyToOne(fetch=FetchType.LAZY)). Is there any way | |
EM.find() is suddenly slower.FIELD) @Column (name = "uid") private String uid; @ OneToOne (fetch = FetchType.EAGER, cascade | |
@Column( name = "columnName") doesn't work, cascade = CascadeType.ALL) @Column( name = "DATA_ITEMS" ) private List dataItems; @ OneToOne (fetch | |
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 | |
LAZY @ManyToOne field functions as EAGER loading in these cases. Regarding your example, ObjectDB can use lazy loading in OneToOne | |
Embedded Entity in EmbeddedId not persisted. Error 631 at select. static class AId { @ OneToOne (cascade = CascadeType.PERSIST)   | |
Failing to read entities under load in multithreaded tests = 6249921651146397564L; @ OneToOne (cascade=CascadeType.REFRESH, fetch=FetchType.EAGER) private TestEntity | |
ArrayIndexOutOfBoundException { @ OneToOne (fetch = FetchType.EAGER) private CacheableJobInfo ji; @ OneToOne (fetch = FetchType.EAGER) private ... . The problem dissapeared when removing the @ OneToOne (fetch = FetchType.EAGER) annotation. I am not | |
NullPointerException when using multithreading private String secondId; @ OneToOne (cascade=CascadeType.ALL) private HashMap myMap; } @Embeddable public class EmbeddableA { @ OneToOne (cascade=CascadeType.ALL) private HashMap myMap; } @Embeddable public class EmbeddableB { @ OneToOne (cascade=CascadeType.ALL) private HashMap myMap; } I'm am trying | |
ClassCastException after upgrade to 2.3.5_03 follows: @Entity public class ObjectDbMessagePayload { @Id String id; @ OneToOne (orphanRemoval=true, cascade=CascadeType.ALL, fetch=FetchType.EAGER) private Object payload; @ OneToOne (orphanRemoval=true | |
Tracking changes to new collections (in enhancement mode) after flush = "uid") private String uid; @ OneToOne (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH ... uid; @ OneToOne (fetch = FetchType.EAGER, cascade = {CascadeType.REFRESH, CascadeType.DETACH }) private | |
Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) simple @ OneToOne relationship fields that likewise become null: private List ownedElements = new ... my larger real-world application, lots of other @OneToMany and @ OneToOne fields are also null). In | |
com.objectdb.o.InternalException: null extends PersistableObject { @ OneToOne (mappedBy = "spouse") private |