When using the new built-in bytecode provider, I get null lazy
collections and uninitialized primary keys, if the entity is lazy. If
I use the old Castle bytecode provider, or not lazy entities,
everything works fine, so I think there's a bug. I may be doing
something wrong, though.
I have a test
This is the current status of this issue:
- If the entity is mapped as lazy and the collection is mapped as
lazy, the collection property is null (!)
- If the entity is mapped as lazy and the collection is mapped as not
lazy, the collection property is null (!)
- If the entity is mapped as not
Why is that? I'm loading it from the DB, NHibernate should create it
itself. In fact, it does, if I don't use lazy loading.
On Apr 8, 12:49 am, belvasis...@googlemail.com wrote:
You have to create the instance of the IEnumerableOrder by yourself so
that NH can use it, just as you would do it
