Internal Website Search
51-100 of 200 resultsDeleting JPA Entity Objects, if any). Orphan Removal JPA 2 supports an additional and more aggressive remove cascading mode | |
Is ObjectDB a NoSQL Database?, but they are easier to use in object oriented languages such as Java. In addition , unlike most other NoSQL databases | |
Shared (L2) Entity Cache; EntityManager instances. In addition to the EntityManager 's L1 cache and the EntityManagerFactory 's L2 | |
JPA Annotations for Relationships annotation enables configuring cascade and fetch policy, using the following enum types: Additional | |
JPA Annotations JPA defines dozens of annotations that can be divided into the following groups: Annotations for JPA aware classes: Annotations for fields in JPA persistable classes: Annotations for additional JPA configuration: Annotations for JPA lifecycle event callbacks: Java EE container annotations: Many | |
ObjectDB Object Database Features Recovery from failure by using a recovery file and double writing. Additional recovery layer | |
ORDER BY clause (JPQL / Criteria API) expression is the primary order expression. Any additional order expression is used to order results | |
JPA Primary Key and additional details. Suppose that queries that retrieve all the events of a specified sensor in | |
Soft Reference Object Cache Recommendation that was small enough to upload. (See attachment.) CBE CBE Additional explanation of the screenshot ... it. support Support Thank you, those responses are helpful. With those, and the additional ... CBE Can you please give additional information about ObjectDB's usage of datastore page cache?  | |
Explorer in 2.3 data and Strings. After playing with it for a while, here is a list of additional features I'd love ... to the database. Again, many thanks for a tremendously useful new addition to ObjectDB. Carl   ... to split the results by id ranges (adding additional top levels to the tree, similarly to viewing | |
Request clarification of changes to accessor enhancement policy (non-getter prefix instead of getter suffix) AND annotations enhanced additional getters/setters, because the additional methods now use (since about version 2-6 ... , so this could still break things and require additional adjustment for specific annotations in the future ... the setters to perform additional tasks such as additional validations and some operations | |
remove & persist in same transaction => Attempt to reuse an existing primary key value Entity (A) with additional data that use an existing ID of another Entity (B) from another class (another table). On this point we get no conflicts. If we remove additional data for Entity (B) and then the special Entity (A) is empty, we remove the special Entity (A). If we add additional data for Entity | |
javax.persistence.Table for the annotated entity. Additional tables may be specified using SecondaryTable or SecondaryTables ... apply in addition to any constraints specified by the Column and JoinColumn annotations and constraints entailed by primary key mappings. Defaults to no additional constraints. Since: JPA 1.0 | |
javax.persistence.PessimisticLockScope. Since: JPA 2.0 Enum Constants EXTENDED In addition to the behavior for PessimisticLockScope.NORMAL ... ) for the entity instance in the additional table(s). Entity relationships for which the locked entity contains | |
javax.persistence.TableGenerator. These are only used if table generation is in effect. These constraints apply in addition to primary key constraints. Defaults to no additional constraints. Since: JPA 1.0 String valueColumnName default "" (Optional | |
javax.persistence.Table.uniqueConstraints generation is in effect. These constraints apply in addition to any constraints specified by the Column and JoinColumn annotations and constraints entailed by primary key mappings. Defaults to no additional constraints. Since: JPA 1.0 | |
javax.persistence.CollectionTable annotation is used on the collection-valued attribute in addition to the ElementCollection annotation ... annotations can be used in addition to the ElementCollection annotation. If the embeddable class | |
javax.persistence.SecondaryTable.uniqueConstraints only used if table generation is in effect. These constraints apply in addition to any constraints specified by the Column and JoinColumn annotations and constraints entailed by primary key mappings. Defaults to no additional constraints. Since: JPA 1.0 | |
javax.persistence.SecondaryTable generation is in effect. These constraints apply in addition to any constraints specified by the Column and JoinColumn annotations and constraints entailed by primary key mappings. Defaults to no additional constraints. Since: JPA 1.0 | |
javax.persistence.TableGenerator.uniqueConstraints JPA Annotation Attribute in javax.persistence.TableGenerator UniqueConstraint [] uniqueConstraints default {} (Optional) Unique constraints that are to be placed on the table. These are only used if table generation is in effect. These constraints apply in addition to primary key constraints. Defaults to no additional constraints. Since: JPA 1.0 | |
javax.persistence.NamedAttributeNode has inheritance, multiple subgraphs can be specified. These additional subgraphs are intended to add ... . These additional subgraphs are intended to add subclass-specific attributes. Superclass subgraph entries | |
javax.persistence.PessimisticLockScope.NORMAL) for the entity instance in the additional table(s). Entity relationships for which the locked | |
javax.persistence.PessimisticLockScope.EXTENDED JPA Enum Constant in javax.persistence.PessimisticLockScope EXTENDED In addition to the behavior for PessimisticLockScope.NORMAL , element collections and relationships owned by the entity that are contained in join tables will be locked if the javax.persistence.lock.scope property is specified | |
javax.persistence.JoinTable.uniqueConstraints JPA Annotation Attribute in javax.persistence.JoinTable UniqueConstraint [] uniqueConstraints default {} (Optional) Unique constraints that are to be placed on the table. These are only used if table generation is in effect. Defaults to no additional constraints. Since: JPA 1.0 | |
javax.persistence.LockModeType successfully. Lock modes must always prevent the phenomena P1 and P2. In addition , calling a lock | |
javax.persistence.JoinTable effect. Defaults to no additional constraints. Since: JPA 1.0 | |
javax.persistence.MapKeyColumn.unique. This constraint applies in addition to any constraint entailed by primary key mapping and to constraints specified at the table level. Since: JPA 2.0 | |
Query.getResultStream() - JPA Method additional capabilities. Return: a stream of the results Throws: IllegalStateException - if called | |
javax.persistence.MapKeyColumn constraint corresponds to only a single column. This constraint applies in addition to any constraint | |
javax.persistence.Query().stream() , however persistence provider may choose to override this method to provide additional | |
TypedQuery.getResultStream() - JPA Method additional capabilities. Return: a stream of the results Throws: IllegalStateException - if called | |
javax.persistence.TypedQuery provider may choose to override this method to provide additional capabilities. Return: a stream | |
Persistence.createEntityManagerFactory(persistenceUnitName,properties) - JPA Static Method: persistenceUnitName the - name of the persistence unit properties Additional - properties to use | |
javax.persistence.Persistence: persistenceUnitName the - name of the persistence unit properties Additional - properties to use when creating | |
EntityGraph.addSubclassSubgraph(type) - JPA Method JPA Method in javax.persistence.EntityGraph Subgraph addSubclassSubgraph ( Class type ) Add additional attributes to this entity graph that correspond to attributes of subclasses of this EntityGraph's entity type. Subclass subgraphs will automatically include the specified | |
javax.persistence.Column in addition to any constraint entailed by primary key mapping and to constraints specified | |
javax.persistence.Column.unique. This constraint applies in addition to any constraint entailed by primary key mapping and to constraints specified at the table level. Since: JPA 1.0 | |
javax.persistence.StoredProcedureQuery().stream() , however persistence provider may choose to override this method to provide additional | |
javax.persistence.NamedEntityGraph [] subclassSubgraphs default {} (Optional) A list of subgraphs that will add additional attributes | |
javax.persistence.NamedAttributeNode.keySubgraph. These additional subgraphs are intended to add subclass-specific attributes. Superclass subgraph | |
javax.persistence.NamedAttributeNode.subgraph can be specified. These additional subgraphs are intended to add subclass-specific attributes | |
javax.persistence.NamedEntityGraph.subclassSubgraphs JPA Annotation Attribute in javax.persistence.NamedEntityGraph NamedSubgraph [] subclassSubgraphs default {} (Optional) A list of subgraphs that will add additional attributes for subclasses of the annotated entity class to the entity graph. Specified attributes from superclasses are included in subclasses. Since: JPA 2.1 | |
javax.persistence.EntityGraph additional attributes to this entity graph that correspond to attributes of subclasses | |
Which API should I use - JPA or JDO? the primary API, and if necessary, switch to JDO as a secondary API for special additional features | |
JDO Reference (JavaDoc) This reference contains the API documentation (similar to JavaDoc) of JDO 2.2. The content is derived from the original JDO documentation with some additions and notes. The most basic JDO types are: All the other JDO types are organized into the following sections: | |
[ODB1] Chapter 7 - JDOQL Queries of the candidate class satisfying the given filter. In addition to these three main components, queries | |
each 1-2 days objects on some objectdb level lock/block each other (and a few seconds could also be considered by users as slow), e.g. by using additional indexes, to prevent ... is received. Each package that is sent has a reply. nevertheless we will add additional protection ... , we'll immediately implement that and feedback results. We already added additional protection | |
javax.jdo.datastore.Sequence.0 Public Methods void allocate (int additional ) Provides a hint to the implementation that the application will need additional sequence value objects in short order. There is no externally ... of obtaining additional sequence value objects. Parameters: additional - the number of additional values | |
javax.jdo.Query the expression are considered to be in the name space of the specified class, with the addition of declared | |
Query.setFilter(filter) - JDO Method the name space of the specified class, with the addition of declared imports, parameters and variables |