I realise this is a diversion, and not an answer to your question (although I think mookid has got that covered). You should really evaluate whether interfaces on your domain entities are actually providing anything of worth; it’s rare to find a situation where you actually need to do this. For example: How is relying … Read more
If you build Fluent from source, there is now support for filters. You use them like this: First create a class inheriting from FluentNHibernate.Mapping.FilterDefinition: using FluentNHibernate.Mapping; namespace PonyApp.FluentFilters { public class PonyConditionFilter : FilterDefinition { public PonyConditionFilter() { WithName(“PonyConditionFilter”) .AddParameter(“condition”,NHibernate.NHibernateUtil.String); } } } In your ClassMap for your class, use the ApplyFilter method: namespace PonyApp.Entities.Mappings … Read more
SetLockMode(LockMode.None) or connection.isolation ReadUncomitted does NOT append a NOLOCK to your queries. Ayende goes into the correct answer on his blog: If you’re using <sql-query> you can do the following: <sql-query name=”PeopleByName”> <return alias=”person” class=”Person”/> SELECT {person.*} FROM People {person} WITH(nolock) WHERE {person}.Name LIKE :name </sql-query> Note the WTIH(nolock) appended to the FROM clause.
Actually the NHibernate reference states that the DateTime nhibernate type will store the .NET DateTime as an SQL datetime truncated at the second level (no millisecond granularity) As such it provides the Timestamp NHibernate type (type=”Timestamp” in the mapping) which will store a .NET DateTime as an SQL datetime without truncation. Note here that an … Read more
You can do something like: config.Mappings(m => { m.FluentMappings.ExportTo(“…file path here…”); m.HbmMappings.ExportTo(“…file path here…”); m.AutoMappings.ExportTo(“…file path here…”); { ); I don’t like it myself. If I find some better way (if such exists at all) I’ll update the answer. See http://blog.jagregory.com/2009/02/03/fluent-nhibernate-configuring-your-application/ Or if broken, see this instead https://github.com/jagregory/fluent-nhibernate/wiki/Database-configuration
NH3 and above allow to correct save entities in case of uni-directional one-to-many mapping without annoying save null–save–update cycle, if you set both not-null=”true” on <key> and inverse=”false” on <one-to-many> FluentNHibernate code snippet for that: public class MasterMap : ClassMap<Master> { public MasterMap() { Id(x => x.MasterId); Map(x => x.Name); HasMany(x => x.Details) .Not.Inverse() //these … Read more
I too have encountered a similar problem and after much experimentation I noticed that when using Nhibernate to generate my schema to a file the generated column type was always length 8000. Setting setting CustomSqlType to Varbinary(max) as suggested above made no difference, however, this work around in my FluentMapping seemed to do the trick: … Read more
Use collection interfaces instead of concrete collections, so NHibernate can inject it with its own collection implementation. In this case, use IList<int> instead of List<int>
Yes its a common problem, you are using the Column “EndDate” twice in your mapping definition (for both Company and PrimaryListing) and that is not allowed. One of them has to go, or have an additional EndDate column (one for each association) check this too nHibernate 2.0 – mapping a composite-id *and* many-to-one relationship causes … Read more
In this case the answer is pretty simple. Do not use many-to-many. Use pairing object. Exactly for the reasons you’ve mentioned: Extend the pairing object with more properties: Check here 24. Best Practices, a cite: Don’t use exotic association mappings. Good usecases for a real many-to-many associations are rare. Most of the time you need … Read more