![]() The collection can also name a which defines the Hibernate Type of the collection elements. You might want to use the JPA annotation is used to specify a custom collection type. See the Database-level checks chapter for more annotation is used to specify an identifier column for an idbag collection. See the Cascading chapter for more annotation is used to specify an arbitrary SQL CHECK constraint which can be defined at the class level. When combining both JPA and Hibernate CascadeType strategies, Hibernate will merge both sets of cascades. CascadeType.LOCK, CascadeType.SAVE_UPDATE, CascadeType.REPLICATE) on a given association.įor JPA cascading, prefer using the instead. See the Caching chapter for more annotation is used to apply the Hibernate specific CascadeType strategies (e.g. See the Batch fetching section for more annotation is used to specify the CacheConcurrencyStrategy of a root entity or a collection. However, if this annotation is used with either value="property" or value="field", it will act just as the corresponding usage of the JPA annotation is used to specify the size for batch loading the entries of a lazy collection. For property/field access type, the JPA should be preferred. ![]() Should only be used to name a custom PropertyAccessStrategy. See the mapping section for more annotation is used to group multiple annotation is used to specify a custom PropertyAccessStrategy. See the mapping section for more annotation is used to provide metadata about an or mapping. You should use either the JPA or the Hibernate native annotation is used to define the any-to-one association which can point to one one of several entity types. I list all the Hibernate mapping annotations for your quick reference :
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |