Databases
StackOverflow2013
Postsdbo
POFluentNHibernate base ClassMap<T> and avoiding the use of typeof(T) to determine entity ID type for defining NHibernate generator
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFluentNHibernate base ClassMap<T> and avoiding the use of typeof(T) to determine entity ID type for defining NHibernate generator
    primarykey
    data
    text
    <p>To centralize some of my logic for each FluentNHibernate class mapping (specifically for mapping auditing properties and the actual primary ID), I've got a base ClassMap called AuditedEntityClassMap which is something like the following:</p> <pre><code>public class AuditedEntityClassMap&lt;TEntity, T&gt; : ClassMap&lt;TEntity&gt; where TEntity : AuditedPersistentObject&lt;T&gt; { public AuditedEntityClassMap() { Cache.ReadWrite(); DynamicUpdate(); ApplyId(); this.ChangeAuditInfo(); } protected virtual void ApplyId() { if (typeof(T) == typeof(int)) map.Id(x =&gt; x.Id).GeneratedBy.HiLo(HiLoConstants.NHibernateHiLoTable, HiLoConstants.NHibernateHiLoColumn, HiLoConstants.NHibernateHiLoMaxLo); else if (typeof(T) == typeof(Guid)) map.Id(x =&gt; x.Id).GeneratedBy.GuidComb(); else throw new InvalidIdTypeInClassMappingException("Invalid type set in class mapping: " + typeof(T)); } } </code></pre> <p>My question is that the type checking of the generic in order to determine the type of NHibernate generator mapping that should be used for it smells and I'm wondering if there's a better way of dealing with it. </p> <ol> <li>The generic type for my domain entities' IDs is used throughout and works great everywhere else (and it's used extensively).</li> <li>I'd prefer not to have to define the ID mapping in every entity's ClassMap if I can avoid it. If this is the only way to do so, I'll live with it.</li> </ol> <p>Thoughts and suggestions?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTed
    1. USTed
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POFluentNHibernate base ClassMap<T> and avoiding the use of typeof(T) to determine entity ID type for defining NHibernate generator
      1. This table or related slice is empty.
      1. VTUndeletion
    2. VO
      singulars
      1. POFluentNHibernate base ClassMap<T> and avoiding the use of typeof(T) to determine entity ID type for defining NHibernate generator
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POFluentNHibernate base ClassMap<T> and avoiding the use of typeof(T) to determine entity ID type for defining NHibernate generator
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload