Hi,

is field property IsDelayLoaded supported in LLBLGENPRO 2.6?

Thanks

Paolo

Is that a Linq to Sql specific thingy? Because it's not linq related.

Otis wrote:

Is that a Linq to Sql specific thingy? Because it's not linq related.

Sorry, I meant the "Delay loaded" property you can explicitly set on fields in Visual Studio LINQ designer. I don't know where I took "IsDelayLoaded" :-)

Bye

Paolo

paolo883 wrote:

Otis wrote:

Is that a Linq to Sql specific thingy? Because it's not linq related.

Sorry, I meant the "Delay loaded" property you can explicitly set on fields in Visual Studio LINQ designer. I don't know where I took "IsDelayLoaded" :-)

Bye

Paolo

The 'linq designer' is the linq to sql designer, so no we don't support that property. 'Delay loaded' means that the entity can be lazy loaded. This is controlled differently in LLBLGen Pro, so there's no equivalent.

Otis wrote:

The 'linq designer' is the linq to sql designer, so no we don't support that property. 'Delay loaded' means that the entity can be lazy loaded. This is controlled differently in LLBLGen Pro, so there's no equivalent.

How is it controlled? My problem is that I have to work with a legacy database with binary fields that I don't want to load every time in the entity, and this feature is great for this purpouse.

Actually it's the only feature that I miss in current version of LLBLGENPRO

Paolo

paolo883 wrote:

Otis wrote:

The 'linq designer' is the linq to sql designer, so no we don't support that property. 'Delay loaded' means that the entity can be lazy loaded. This is controlled differently in LLBLGen Pro, so there's no equivalent.

How is it controlled? My problem is that I have to work with a legacy database with binary fields that I don't want to load every time in the entity, and this feature is great for this purpouse.

Actually it's the only feature that I miss in current version of LLBLGENPRO Paolo

It's called ExcludeFields You can specify which fields to exclude (or which fields to include and thus exclude the rest) and later on fetch them into entities. See docs: using the generated code -> Adapter / Selfservicing -> Excluding / including fields for fetches.

You can also specify this in linq queries of course, See the Linq to LLBLGen Pro docs in the v2.6 manual for details. (General usage section)