If you haven't told NHibernate about ParentEntityReference in any way, then
it will of course be null.
"mapping is one way". But your classes have a bidirectional relationship -
why not tell NHibernate about this?
Another way is to set ParentEntityReference inside the setter for
ParentEntity.Comp
I have post the same twice but I believe that second one is more accurate
https://groups.google.com/forum/?fromgroups=#!topic/nhusers/j1N1IY5PBBc
Regards
On Sunday, November 18, 2012 3:30:14 AM UTC+1, guilemsola wrote:
>
> Hi All,
>
> I'm suffering an issue with NH and oracle running out of cur
So I have done some more experimentation. It seems that *all* properties
that are set inside the constructor, are set to null (if applicable).
Is there a way to set properties inside the constructor of the entities
when using NHibernate?
On Wednesday, November 14, 2012 11:23:50 PM UTC+2, Mike B
Hi All,
I'm suffering an issue with NH and oracle running out of cursors (a
thousand). My application does a lot of tracking in database, it's
multithreaded and with some concurrence I'm running out of cursors. I'm
using regular and stateless sessions and I'm almost shure that I close all
them
Hi All,
I have a multithread application with threadstatic sessions that does some
job with files. It's using NH to consume from services and running on an
oracle db, so far so good.
Every thread has a verbose log that uses stateless session to be more
lightweight. BTW when some files are pro
