Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 160691
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 11, 20262026-05-11T11:04:48+00:00 2026-05-11T11:04:48+00:00

I have a read-only database, so I am turning off ObjectTracking (thus implicitly turning

  • 0

I have a read-only database, so I am turning off ObjectTracking (thus implicitly turning off DeferredLoading).

I wish to do lazy loading and not use LoadWith<>.

What is the simplest way to explicitly tell Linq to go and lazy fetch a relation just before I need the data itself.

For example: a simple dbml alt text

If I have the following code:

  TestDbDataContext context = new TestDbDataContext(Settings.Default.TestersConnectionString);   context.ObjectTrackingEnabled = false;    var result = context.Employees.ToList();   foreach (var employee in result)   {     // HERE Should load gift list     foreach (var gift in employee.Gifts)     {       Console.WriteLine(gift.Name);     }   } 

I know I can write a full query again, but I hope we can find together a better way.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. 2026-05-11T11:04:48+00:00Added an answer on May 11, 2026 at 11:04 am

    You are fighting the system… 2 thoughts:

    • if you know you need the other data (nested foreach), why wouldn’t you want to use LoadWith? That is pretty-much the text-book use case
    • since you (from post) know that object tracking is required for lazy loading, why not just enable object tracking; data-contexts should usually be considered ‘units of work’ (i.e. short-lived), so this isn’t likely to hurt much in reality.

    See the official replies here for why these two options (object tracking and deferred loading) are linked.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a set of files. The set of files is read-only off a
I have read-only access to a database that was set up for a third-party,
We have a large read only secondary database file. We have several different copies
I have a Core Data-based iPhone app with a pre-populated read-only database. What protection
Some users will use the database as read-only and some will need to add,
I have a read only database (product) that recides on its own Sql Server
I have several tables in my database that have read-only fields that get set
I have read only permission on a SQL Server 2005 database, and I'm looking
I use the following code to only read the database.... NSString *databasePath = [[[NSBundle
I have a class that defines a read-only property that effectively exposes a private

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.