I would start with the enums and CustomType<long>() it maybe that the NH is trying to convert a string to a int, string to enum or int to enum, etc. I would drop some of the inheritance. it looks like overkill (blindly applied advice). don't add it until it's needed. otherwise you are introducing unnecessary complexity. with the domain it's just noise, but the mappings could be producing the problems.
you can also use NHProf ($) to diagnose NH health. with this tool you can see the insert and select commands executed by NH. this my provide some insight into why the insert "works" but the select does not. Another configuration to consider after this issue is solved: lazy="false" most times this is a hurts preformance more than it improves development. If you try to map the entire domain and then test for mapping errors you will drive yourself crazy. if you incrementally add mapped properties/classes and support them with regression tests it will be easier to diagnose problems and extend the domain. there isn't a need to debug/step through NH unless you want to understand how NH works. That's easier to do reviewing the unit tests and code base, rather than stepping through the code. On Sep 15, 3:13 am, Lorenzo Vegetti <[email protected]> wrote: > Now, what could be wrong? It's 2 days I've been looking at the code, > and I guess that there's something I don't know (maybe related to the > Editions set collection, or with the enum fields, there's 3 of them) > or something obvious I'm overlooking... > > I also have a question that is more or less related to this one: I use > VS2010 and I couldn't find a way to debug the code generated by NH at > runtime using Emit... is there a way to step in that code? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
