Is there a scenario where eager loading is preferred ove开发者_高级运维r lazy loading?You may require a fully populated object graph before passing it to another layer i.e. when working with what NHib
I have a property on my domain object which is exposed as this: public virtual IEnumerable<WorkPost> WorkPosts
I am working on a API to access data stored in a syste开发者_JS百科m. The system contains things like people, appointments and procedures associated with those appointments. My application will strict
I implemented lazy image load for my UITableView using NSUrlConnection. This is all working very nicely. When I open my table, I automatically get the images when I wait for a second (on 3G). However,
I am binding WPF with Entity-Framework. The Window.DataContext property is set to a Quote. This Quote has a property Job, that I have to trigger Quote.JobReference.Load it should load from the server
I am fetching a lot of thumbnails in my application from a remote server and lazy-loading these in a list view.
By default,开发者_StackOverflow社区 NHibernate lazy loads all collections, which works fine for me in most cases. However, I\'m running into problems with some tools that use reflection, which doesn\'
I have a generic repository and when I\'m using a DoQuery method to select objects from the database, I need to load some of the related entities in order to开发者_如何学Go not get nulls in the place
First of all, I\'m using Fluent NHibernate with LinqToNHibernate. I\'ve got a query to do a search on a table based on what data the user entered.So, for example, I\'m doing something like this:
I have currently moved my blogengine over from Linq2Sql to NHIbernate. I\'m stuck at the following performance problem: