lazy-loading

If have an entity A with a bidirectional one-or-zero-to-one mapping with entity B. The mapping is as follows: <class name="EntityA" table="TABLE_A" mutable="true" lazy="true"> <id name="idA" type="long" column="pk_a" unsaved-value="null"> <generator class="sequence"> <param name="sequence">pk_a_seq</param> </generator> </id> <one-to-one name="propertyB" class="EntityB" property-ref="propertyA" constrained="true" outer-join="false"/> </class> and <class name="EntityB" table="TABLE_B" mutable="true" lazy="true"> <id name="idB" type="long" column="pk_b" unsaved-value="null"> <generator class=

I'm following the fairly standard L2S repository pattern, using the following as one of the methods public IEnumerable<T> GetAllByFilter(Func<T, bool> expression) { return _dataContext.GetTable<T>().Where(expression); } I'm a bit miffed to see that the call to GetTable appears to literally get the table, with the Where expression presumably evaluated in-memory afterwards. So a simple call like var order = GetAllByFilter(o => o.OrderNumber == 1); which should only ever return one record, is fetching the entire 50000 record database. Is Linq normally this bad? Or am I missing something? Change:

My object looks something like this: class { int a; object b; IList<string> c; } All the fields are getting populated from the database and the collection is getting lazy initialization which is desirable. Now, my problem is that I want to send this object to the web service. But since the collection is lazily loaded, am not able to do it. Can somebody please give me an idea or a direction or some example code which I can look into for my problem. I want a generic way to force initialization for this list before I send it over the wire. Also, I have multiple objects like this so a generic way

Angular2 lazy loading a route issue. I'm using Angular2, typscript, html5 and systemjs. I'm trying to get lazy loading working for one of my basic routes. This is the blog I'm following but I can't seem to get it working: http://blog.angular-university.io/angular2-ngmodule/ This is the console error I get: Uncaught (in promise): Error: Cannot match any routes. URL Segment: '500' My page is the 500 page. Below I have added my files at there current state. Module for 500 page: import { NgModule } from '@angular/core'; import { RouterModule } from '@angular/router'; import { Component500 } from '

I basically have a booking engine unit results page which must show 40 units and per each unit there's 1 large image of the first thumbnail and an X number of accompanying thumbnail images. I've been using the jquery lazy load plugin, but it's not thorough enough ( I'm invoking it on DOM Ready ), plus it doesn't really work in IE ( 50% of the clients use IE so it's a big issue ). What I think I really need to do is not really spit out the image but a fake element such as a span, and possibly modify my code such that if the user views the span, render it into an image element. <span src="

I know that this has been discussed lot of times. I just can't understand how this work or where my mistake is. I think giving you a reduced example is the best way to show you what I'm trying to do and what assumptions I'm taking... I have a Product class with a name. The name is a String property that is lazy. My DAO: public abstract class HibernateProductDAO extends HibernateDaoSupport implements ProductDAO { public List getAll() { return this.getHibernateTemplate().find("from " + this.getDomainClass().getSimpleName()); } } My Service Interface: public interface ProductService { //This

I have used the Eclipse plugin Visual Editor to construct Java Swing interfaces. As I'm not a big fan of the code WYSIWYG (UI) editors generate, I wanted to optimize it, when I noticed, that the editor implemented all elements using lazy loading like this: private JPanel getSomePanel () { if ( somePanel == null ) { somePanel = new JPanel(); // construct the panel } return somePanel; } I know that lazy loading is used to get better performance, when the objects in question are not used immediately. However for most user interfaces this makes less sense, as a window for example should usually