Need help with Hibernate? Read this first:
http://www.hibernate.org/ForumMailingli ... AskForHelp

Hibernate version: 1.0.2 alpha

Every many-to-one association in my project seems to have the same problem. Lets suppose two objects, A and B.

A many-to-one B

If I try to use A.B, and B is not null, the attributes of B are not setted but the properties are. Something like, (attribute)B.id = 0 and (Property)B.Id = 34.

But if I use B before accessing it through A, B.id = 34 and B.Id = 34.

Anyone knows what's happening? It only happens in my many-to-one associations. Everything else seems fine.

Thank you.

you can set b' lazy false.

You're right. I found that outer-join="true" in the relationship works too. Do you know if there is any difference between them? I think that lazy="false" is a good option if we're sure that we want it working in all relations, so we don't have to specify the outer-join in all relations. Am I right?

Thank you.

by default in NH 1.0.2 the relationships are set lazy="false". instead of changing this behavior, i would encourage you to read up on sessions and lazy loading (Session.Lock() is one place to look) to truly understand where you want the collections to be loaded lazily and where you don't. otherwise you are condeming your app to load an entire object graph every time when it might only want the parent object. plus you won't gain the benefit of second-level caching if you decide to use that someday.

-d

But I'm not talking about collections. My problem is exactly at the other side of the relationship. The collections are ok with lazy enabled. I don't know if I am clear enough in the first message. Please, let me know.

Thank you.

No that was my fault in miscommunicating.

Re-reading your post, I think what you are calling an "attribute", I might call a "member variable":


Relationships (including 1-M and M-1) are lazily loaded by default so calling A.B.ID on the associated object forces NH to load the lazily loaded association of A to B. Calling A.B.id first of all is bad programming style, second would not have access to the reflected property methods that would trigger the load, I think.

I may have misunderstood your use of the word attribute and aplogize if that is so, but if I haven't and you are declaring your member variables as anything other than private (or protected in certain inheritance situations), then you should consider changing that.
-d

You got it now devonl. Let's use "member variable" from here. :) My english is not so good.

You're right. My member variables are all private, but I need to access them inside their classes. Let's suppose:



The only member variables with value were the enums.

and...

//Suppose Get is a function and 5 is the id
//Here, price in b is ok , b.Price is ok and b.TotalPrice is ok
B b = Get(B, 5);

but...

A a = Get(A, 6);
//Now internally b.price = 0 but b.Price is ok

//so
double price = a.b.Price; //ok

double totalPrice = a.b.TotalPrice // not ok because it used price internally


This issue was solved as described above, but is this correct?

Lazy and proxies are the "problem".

Thank you.