This question is purely academic, because I\'d never dream of doing this in real code.
Using LINQ to SQL, I want to bind an IQueryable
The sole effect of that using block is to limit the lifespan of ctx
to the block itself.
The useful lifespan of iq
is dependent on the lifespan of ctx
. You are explicitly disposing of ctx
before iq
is ever used.
The way to fix the problem would be to get rid of the using block, or to force iq
to evaluate within the block (e.g. iq = iq.ToList()
), and return only the results of that evaluation. If you're not keen on doing the latter, just ditch the using. ctx
will be disposed of at some point after nobody needs it. Not perfect, maybe, but that's life with a garbage collector. Are you sure it'll be creating a problem if it stays around? Don't fix what's not yet shown to be broken.
public IQueryable MembershipGetAll()
{
var obj = (from mem in db.GetTable<MEMBERSHIP>()
select new
{
NAME = mem.MEMBERSHIP.NAME,
TYPE = mem.MEMBERSHIP.TYPE,
TAX_ID = mem.TAX_RATE.TAX_ID,
DISCOUNT = mem.DISCOUNT,
DISCOUNT_PERCENT = mem.DISCOUNT_PERCENT,
}
).AsQueryable();
return obj;
}
private void LoadMembership()
{
IQueryable mem = null;
mem = eb.MembershipGetAll();
grdMembership.DataSource = mem;
grdMembershipRates.DataBind();
}
Just do it like this
You can think of the IQueryable as the instructions required to execute the query. When you call .ToList(), you are executing the IQueryable() to return actual data. When you bind to IQueryable(), it will expect to have a data source to get the actual data whenever DataBind() is called.
When you set gvGenre.DataSource() = Genre.GetGenres2(), the DataContext required to get actual data based on your IQueryable is destroyed before the call to DataBind() occurs.
It works if you call .ToList() because you're physically going out and getting the data, then putting it memory.
Storing the IQueryable is like storing just the query. You can't execute a query if the datasource it expects to work with doesn't exist.