Home » Search

About schema

51-60 of 200Refresh
JPA Doc
7

javax.persistence.SecondaryTable

the primary table. Default value: {} Since: JPA 1.0 String schema (Optional) The schema of the table. (Optional) The schema of the table. Defaults to the default schema for user. Default value
JPA Doc
7

javax.persistence.TableGenerator

: "" Since: JPA 1.0 String schema (Optional) The schema of the table. (Optional) The schema of the table. Defaults to the default schema for user. Default value: "" Since: JPA 1.0 String table (Optional) Name
JDO Doc
6

javax.jdo.annotations.PersistenceCapable

an extent. Default value: "" Since: JDO 2.1 String schema Schema to use for persisting this class or interface. Schema to use for persisting this class or interface. Default value: "" Since: JDO 2.1
JPA Doc
6

javax.persistence.SequenceGenerator

one or more classes to be the generator for primary key values. Since: JPA 1.0 String schema (Optional) The schema of the sequence generator. (Optional) The schema of the sequence generator. Default
JPA Doc
6

javax.persistence.spi.PersistenceUnitInfo

getPersistenceXMLSchemaVersion() Returns the schema version of the persistence.xml file. Returns the schema version of the persistence.xml file. Returns: persistence.xml schema version Since: JPA 2.0 Properties
JPA Doc
5

GenerationType.AUTO

on how to create such resources in the event that it does not support schema generation or cannot create the schema resource at runtime. Since: JPA 1.0
JPA Doc
5

getPersistenceXMLSchemaVersion()

Method javax.persistence.spi.PersistenceUnitInfo String getPersistenceXMLSchemaVersion() Returns the schema version of the persistence.xml file. Returns: persistence.xml schema version Since: JPA 2.0
JPA Doc
5

javax.persistence.GenerationType

such resources in the event that it does not support schema generation or cannot create the schema
Forum
4

Persist not working when ObjectDB and another db is used in the same application (through spring) with different tx managers

Forum
4

PersistenceException: Failed to locate field

Hi, have recently been running into this issue when changing the schema: com.objectdb.o ... . pretty sure that in the past schema evolution would not have triggered errors, is this case, a simple new ... . Specifically, from: http://www.objectdb.com/java/jpa/entity/schema "Fields in the new schema