I am seeing child collections issue database calls on new objects.

i.e. WebOrderEntity wo = new WebOrderEntity(); int x = wo.WebOrderFile.Count(); //Causes select from database where parent id = 0

This topic: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=15181&HighLight=1 indicates 2.6 fixed this, but it seems to be back in 3.0?

SD.LLBLGen.Pro.ORMSupportClasses.NET20 - 3.0.10.915 Designer is the August 18th build.

We are looking into this trying to reproduce it.

I reproduced your problem with v3 latest version. We are looking into this. In the meantime please use this code (not ideal, but it works):

WebOrderEntity wo = new WebOrderEntity();
wo.AlreadyFetchedWebOrderFile = true;
int x = wo.WebOrderFile.Count(); 

It looks like this wans't added to v2.6 due to customer requests (some customers want this): http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=15753&StartAtMessage=0&#87864

Indeed, we didn't add it in v2.6/3.0. (3.0 mainly due to time constraints, as we focused on the designer mainly).

I've added a workitem to the v3.1 queue so it will be added in v3.1 with a setting. v3.1 is scheduled to go beta in december. (the setting is off by default, and can be enabled). In the mean time please use the workaround mentioned in the threads.

I had not thought of setting the key, then calling the property. Makes total sense, in fact I do it myself.

It seems the best way to handle this would be to not load relationships where the entities PK is used and the entity is new. This should always result in a no-op.

If the new setting could work that way, it would be great. Should cover both cases pretty well.

I think it can be implemented like that.

Thanks.

Awesome