.
thanks.
Łukasz Podolak
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate@googlegroups.com.
To unsubscribe from this group, send email to
fluent-nhibernate+unsubscr...@googlegroup
I have just found the same problem with my mappings, that come from
multiple assemblies, how should we handle this situtation ?
thanks,
Łukasz Podolak
On 7 Lip, 14:09, Roberto Hernández wrote:
> Can the .UseOverrideFromAssemblyOf setting be specified multiple times in
> a
Hi guys,
I'm currently having the same problem as was described in this post:
http://groups.google.com/group/fluent-nhibernate/browse_thread/thread/15fdb057ec89078e?pli=1
When I use IAutoMappingOverride and start defining my subclasses I end
up with duplicate mappings - those joined subclasses t
ontention, one of the reasons why the table per
> class hierarchy is default, is because it's the easiest to use in the
> database, and it's also the best performing option. Having done a fairly
> complex system using both ways, the table per class hierarchy is far better
> per
By default, the inheritance mapping is "table per class hierarchy". I
have a "DictionaryBase" class and couple of derived classes from it.
How can I tell fnh to map all my derived classes as single tables and
not to map DictionaryBase at all ? Can be fluent or automapping,
whichever gets job done.
new NHibernate.Tool.hbm2ddl.SchemaExport(config).Create
(true, true);
---
I know it's a lot of code that I vomit here (extremely sorry) but I
wasted half a day on searching for the solution and I'm still stuck on
this. Could anybody point me where am I wr
