Hi!

We're using LLBL 2.5 Final, Adapter template group, C#, .NET 3.5 platform and Oracle as the DB.

We have a UserDataEntity which holds some data on our active user, and which is bound through a 1:1 relation to a UserSettingsEntity object that holds the app settings for the user (the settings are stored as an XML in a CLOB, so it's only that one entity in the settings table that I need to fetch and nothing more). Up until recently we generated the UserDataEntity class to contain the UserSettings property, mapped on the relation, even though we never actually used it. The settings were loaded with this code:

UserSettingsEntity settings = adapter.FetchNewEntity<UserSettingsEntity>(UserDataEntity.Current.GetRelationInfoUserSettings());

The loaded settings were read and discarded, never stored in the UserDataEntity.Current.UserSettings property. When we chose to generate the code without the UserSettings property (we were cleaning up, a lot of these fields mapped on relations were unneccessary to us), suddenly the generated UserDataEntity class didn't have the GetRelationInfoUserSettings() method.

In short - if we don't generate the field mapped on the relation, why don't we still get the accompanying GetRelationInfo...() method? It would still be very useful regardless of the property's existence, IMO.

I would appreciate any help in clarifying this, or perhaps if someone knows whether there's another (simple ) way to get an IRelationPredicateBucket for the purpose of the above query?

Josip Bakic

Did you hide the relation on either side of it?

Nope, I checked that.

josip, you should create your own IRelationPredicateBucket: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=6581&StartAtMessage=0&#36694

Thank you!

Although I find the explanation for not generating the GetRelationInfo...() methods given in the other thread to be a little odd. "The name has no meaning" - how so? Even though no property is generated, the name of the property is known to the LLBL project...

Yes it is 'known' but only because the designer doesn't remove the relations as it then would have a problem when the project is refreshed. So it simply hides them instead of removes them/ Hiding relations is equal to removing them for the designer and code generator: the relation doesn't exist.

I'm sorry if my questions are bothersome, but I still don't quite get it. The UserDataRelations class in the generated code contains info on this relation, even though it "doesn't exist", and I presume I could even write a general method for creating an IRelationPredicateBucket based on this info and an entity, right?

In the end, we enabled the fields on the relations which we plan tu use, it's not really a big problem. I'm just curious about why this happens..

josip.bakic wrote:

I'm sorry if my questions are bothersome, but I still don't quite get it. The UserDataRelations class in the generated code contains info on this relation, even though it "doesn't exist", and I presume I could even write a general method for creating an IRelationPredicateBucket based on this info and an entity, right?

In the end, we enabled the fields on the relations which we plan tu use, it's not really a big problem. I'm just curious about why this happens..

Oh, I'm sorry, I didn't read the first post properly. My bad

It removes this method as it's not really necessary, as the method is there for fetching the related entities for the field mapped onto the relation. The method for example adds a predicate on the PK field value of the entity you call the method on in some relation variants, (m:1, 1(fk):1(pk)). If you don't have the field, why do you need the method, as the advantage of having the field is to work with related entities more easily.

Well, it's just that the field I don't really need, but the method I do. But I can't really think of a good example right now

Thank you for your answer!