Home » Search

About addition

111-120 of 200Refresh
JPA Doc
2

javax.persistence.TransactionRequiredException

throwable" that predates the addition of chained exceptions to Throwable. Note that it is not
JPA Doc
2

JoinTable.uniqueConstraints

Annotation Element javax.persistence.JoinTable UniqueConstraint[] uniqueConstraints (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. Default value: {} Since: JPA 1.0
JPA Doc
2

MapKeyColumn.unique

addition to any constraint entailed by primary key mapping and to constraints specified at the table level. Default value: false Since: JPA 2.0
JPA Doc
2

PessimisticLockScope.EXTENDED

Enum Constant 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
JPA Doc
2

PessimisticLockScope.NORMAL

) for the entity instance in the additional table(s). Entity relationships for which the locked entity
JDO Doc
2

setFilter(filter)

, with the addition of declared imports, parameters and variables. As in the Java language
JDO Doc
2

javax.jdo.Query

space of the specified class, with the addition of declared imports, parameters and variables. As in
Forum
2

Soft Reference Object Cache Recommendation

.) Additional explanation of the screenshot of post #1 is needed. Does it show the byte[] that is not released ... .  With those, and the additional testing I have been doing, I think the best approach is to use soft references and tune the JVM. Can you please give additional information about ObjectDB's usage of datastore page cache?  I
Forum
1

Explorer in 2.3

data and Strings. After playing with it for a while, here is a list of additional features I'd love ... .   Again, many thanks for a tremendously useful new addition to ObjectDB. Carl   Thank ... (adding additional top levels to the tree, similarly to viewing a very large array in the debugger
Forum
1

remove() and persist() in same transaction => Attempt to reuse an existing primary key value

(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