What's new in NHibernate support in LLBLGen Pro v5.8
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.8
No additions have been made for NHibernate support in v5.8.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.7
No additions have been made for NHibernate support in v5.7.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.6
No additions have been made for NHibernate support in v5.6.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.5
No additions have been made for NHibernate support in v5.5.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.4
- All regions have been removed from the generated code.
- PostgreSQL 10x is now a supported database.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.3
- It's now possible to specify whether a normal field in an entity should be lazy loaded, using the field setting LazyLoadField. Default is false.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.2
No additions have been made for NHibernate support in v5.2.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.1
No additions have been made for NHibernate support in v5.1.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v5.0
Caching directives (settings)
It's now possible to specify cache usage and cache region values for entity mappings, using the defaults CacheUsageDefault and CacheRegionDefault, which control the entity specific settings CacheUsage and CacheRegion resp.
The following changes / additions were made in the NHibernate support in LLBLGen Pro v4.2
- NHibernate v4.x support.
- For string fields, the length is now emited in the mapping files, if the length is smaller than 4000. If the length is larger than 4000 it's left to NHibernate and no length attribute/method call is emited.
- Readonly entities are now supported. See the 'Allowed action specification per entity mapping' feature in the designer documentation for details.