This extension specifies how to eagerly fetch subclass state. It overrides the global kodo.jdbc.SubclassFetchMode property. Set the JPA kodo.persistence.jdbc.SubclassFetchMode annotation to a value from the kodo.persistence.jdbc.EagerFetchType enum: JOIN, PARALLEL, or NONE. Set the JDO jdbc-subclass-fetch-mode XML extension key to join, parallel, or none. See Section 5.7, “Eager Fetching” for a discussion of eager fetching.

The kodo.persistence.jdbc.Strategy class annotation allows you to specify a custom mapping strategy for your class. See Section 7.10, “Custom Mappings” for information on custom mappings. Note that this extension applies only to JPA mapping; when using JDO mappings you specify custom class strategies using the standard XML inheritance element's strategy attribute.

The kodo.persistence.jdbc.DiscriminatorStrategy class annotation allows you to specify a custom discriminator strategy. See Section 7.10, “Custom Mappings” for information on custom mappings. Note that this extension applies only to JPA mapping; when using JDO mappings you specify custom discriminator strategies using the standard XML discriminator element's strategy attribute.

The kodo.persistence.jdbc.VersionStrategy class annotation allows you to specify a custom version strategy. See Section 7.10, “Custom Mappings” for information on custom mappings. Note that this extension applies only to JPA mapping; when using JDO mappings you specify custom version strategies using the standard XML version element's strategy attribute.

This extension specifies how to eagerly fetch related objects. It overrides the global kodo.jdbc.EagerFetchMode property. Set the JPA kodo.persistence.jdbc.EagerFetchMode annotation to a value from the kodo.persistence.jdbc.EagerFetchType enum: JOIN, PARALLEL, or NONE. Set the JDO jdbc-eager-fetch-mode XML extension key to join, parallel, or none. See Section 5.7, “Eager Fetching” for a discussion of eager fetching.

All fields in Java are polymorphic. If you declare a field of type T, you can assign any subclass of T to the field as well. This is very convenient, but can make relation traversal very inefficient under some inheritance strategies. It can even make querying across the field impossible. Often, you know that certain fields do not need to be entirely polymorphic. By telling Kodo about such fields, you can improve the efficiency of your relations.

	Note
	Kodo also includes the type metadata extension for narrowing the declared type of a field See Section 6.4.2.7, “Type”.

Kodo JPA defines the following extensions for nonpolymorphic values:

The value of these extensions is a constant from the kodo.persistence.jdbc.NonpolymorphicType enumeration. The default value, EXACT, indicates that the relation will always be of the exact declared type. A value of JOINABLE, on the other hand, means that the relation might be to any joinable subclass of the declared type. This value only excludes table-per-class subclasses.

Kodo JDO defines the following nonpolymorphic mapping extension keys:

These keys apply to field values, collection or array elements, map keys, and map values, respectively. Set the extension value to exact to indicate that the relation is always to the exact declared type. Set it to joinable if the relation can be to any joinable subclass of the declared type. A value of joinable only excludes table-per-class subclasses.

This family of boolean extensions determines whether Kodo will use the expected class of related objects as criteria in the SQL it issues to load a relation field. Typically, this is not needed. The foreign key values uniquely identify the record for the related object. Under some rare mappings, however, you may need to consider both foreign key values and the expected class of the related object - for example, if you have an inverse relation that shares the foreign key with another inverse relation to an object of a different subclass. In these cases, set the proper class critera extension to true to force Kodo to append class criteria to its select SQL.

Kodo JPA defines the following class criteria annotations for field relations, array, collection, and map element relations, and map key relations, respectively:

Kodo JDO defines the following class criteria mapping extension keys for field relations, collection and array element relations, map key relations, and map value relations, respectively:

Kodo's family of strategy extensions allow you to specify a custom mapping strategy or value handler for a field. See Section 7.10, “Custom Mappings” for information on custom mappings.

Kodo includes the following JPA strategy annotations:

Kodo recognizes the following JDO strategy extension keys:

Boolean extension dictating whether the current mapping can insert into this column.

Boolean extension dictating whether the current mapping can update this column value.

This extension is only valid on version columns. When you use custom lock groups, it allows you to declare which version column is for which lock group. See Section 5.8, “Lock Groups”.