About generated

161-170 of 200Refresh
JDO Doc
2

Value.generateForeignKey

Annotation Element javax.jdo.annotations.Value String generateForeignKey Generate or assume a foreign key constraint exists on the column or columns associated with this join. Specify "true" or "false". Returns: whether to generate or assume a foreign key constraint Default value: "" Since: JDO 2.1
Issue
2

ObjectDB-2.6.9: Failed to commit transaction: Failed to set numeric value of field property Element.id using reflection

) at com.greensoft.objectdb.test.mini.ejb.__EJB31_Generated__Builder__Intf____Bean__.createProject ... , and then irrelevant checks are performed by ObjectDB. For example when setting a generated primary ... web application it gets further then it still fails with a family of generic value-wrapper entity
Forum
1

@SequenceGenerator and single id in whole database

of my model enitities, but it looks like id's are generated using only one, shared generator. Is there any other way to use separate generators for each entity, so that each entity uses its own sequence just like in RDBM? You can use different generators for different entity classes: By using multiple
Forum
1

Query results are not up to date for entities, not primitives

generic functions to build generic TypedQuerys. I just realized that the data retrieving up to date if I do not use the generic on parameters of JPA functions! This is the update: em .createQuery ... ")   I really need to use my generic functions to build the typedquerys! After such an update queries
JPA Doc
1

Basic.optional

Annotation Element javax.persistence.Basic boolean optional (Optional) Defines whether the value of the field or property may be null. This is a hint and is disregarded for primitive types; it may be used in schema generation. If not specified, defaults to true. Default value: true Since: JPA 1.0
JPA Doc
1

CollectionTable.uniqueConstraints

Annotation Element javax.persistence.CollectionTable UniqueConstraint[] uniqueConstraints (Optional) Unique constraints that are to be placed on the table. These are only used if table generation is in effect. Default value: {} Since: JPA 2.0
JPA Doc
1

Column.insertable

Annotation Element javax.persistence.Column boolean insertable (Optional) Whether the column is included in SQL INSERT statements generated by the persistence provider. Default value: true Since: JPA 1.0
JPA Doc
1

Column.precision

Annotation Element javax.persistence.Column int precision (Optional) The precision for a decimal (exact numeric) column. (Applies only if a decimal column is used.) Value must be set by developer if used when generating the DDL for the column. Default value: 0 Since: JPA 1.0
JPA Doc
1

Column.updatable

Annotation Element javax.persistence.Column boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider. Default value: true Since: JPA 1.0
JDO Doc
1

DatastoreIdentity.customStrategy

Annotation Element javax.jdo.annotations.DatastoreIdentity String customStrategy Custom strategy to use to generate the value for the identity. If customStrategy is non-empty, then strategy must be UNSPECIFIED. Returns: the custom strategy Default value: "" Since: JDO 2.1