In my scenario - I ended up disabling lazy-loading (as in first post) and now I load entity on demand controlling async behavior.. 

 

If you haven't changed the reference strategy, the call to SysDocument.SysFile will lazily load the SysFile.  If you've set the reference load strategy to DoNotLoad, which you did in an earlier post, then the SysFile won't be retrieved.   DevForce scalar navigation properties don't return null, they return a null entity if no entity exists.   More here - http://drc.ideablade.com/xwiki/bin/view/Documentation/null-entity.

 

Also remember that if you're working in Silverlight all lazy loads are asynchronous.  When called, these properties return a pending entity or pending entity list.

 

 

 

How do I programmaticaly fetch it? In my case I have SYSDocument which describes document properties. It's child entity is SYSFile - this is table where I store blobs.

 

User wants to download file and I need to bring this SYSFile to the client. If I just access SYSFile.Data property in code than I get empty byte array (byte[] Data), it's not lazy loaded.

 

I tried to run code like this but it didn't work either:

var query = documentPlacement.SYSDocument.SYSFile.ToQuery();
            query.ExecuteAsync(
                op =>
                    {
                        if (op.HasError)
                        {
                            var aa = op.Error;
                        }

                        var a = op.Results;
                        var b = a;
                    });

 

op.Results is empty. I understand that I can write query to fetch it myself. But how do I know that I need to fetch it? SYSDocument.SYSFile is always present (not NULL). How to programmaticaly determine if this entity loaded?

 

 

 

 

Is there any way for me to trace who is accessing this entity to see why it's doing it? I like lazy loading behavior when I need entity but in this case it doesn't seem to be needed..

 

You might be seeing lazy loading occur for data loaded into a grid, particularly when columns are auto-generated.  For example, if displaying Order information and using auto-generated columns, the OrderDetails for each order will be lazily loaded.

 

As you've noted, you can use the ReferenceStrategy to change the loading behavior for navigation properties.  Here's more information - http://drc.ideablade.com/xwiki/bin/view/Documentation/navigation-properties-data-retrieval.

 

I have table Document and table File. File contains binary data and I don't want it to load unless I need this data.

 

SYSDocument.PropertyMetadata.SYSFile.ReferenceStrategy = new EntityReferenceStrategy(EntityReferenceLoadStrategy.DoNotLoad, MergeStrategy.OverwriteChanges);

After placing code above it works (entity not loaded) and no errors which proves me that my code doesn't need "File" just yet. No bindings, nothing needs it.

 

Question is, what triggers lazy loading and how I can see which line of code caused lazy loading to happen? I like the feature but also want to be able to contol it. Or at least understand why DevForce decides to load it.