LINQ to SQL Instantiation: ASP Alliance

Print Add To Favorites Email To Friend Rate This Article
LINQ to SQL Instantiation

page 6 of 8

by Brian Mains
Feedback

Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 37749/ 154

Article Contents:

Query Operations

When using an operation like the Where() method in the following code:

Listing 8

_context.Customers.Where(i => i.AccountNumber == "T2341003");

The results that come back are a DataQuery object. This object is not null for queries that even return no results. So the following code works:

Listing 9

customers = _context.Customers.Where(i => i.AccountNumber == "XXXX");
Assert.AreEqual(0, customers.Count());
 
count = 0;
foreach (Customer customer in customers)
{
      count++;
      //Test that iterating through collection is OK
}
Assert.AreEqual(0, count);

What this means is that the Where() method returns no records, because the account number does not exist. The result count is an empty query, but you can continue to use this object freely, as shown above, and not have to worry about a null reference exception.

« (Page 5)

View Entire Article

(Page 7) »

User Comments

Title: Another way to do this...?
Name: Funka!
Date: 2009-08-14 5:17:13 PM
Comment:
Another possibility it seems is to create a partial class and partial method "OnCreated" ?
For example:
public partial class Order
{
partial void OnCreated()
{
_OrderKey = Guid.NewGuid();
_CreatedDate = DateTime.Now;
}
}
This way, you don't need to keep remembering to do this every time you instantiate an object.

It should also be noted that you avoid your specific error (but not the general need for setting default values) by setting the LTS entity property's "Auto Generated Value" to true --- LTS will know not to supply a value to these columns when inserting, so you can just let SQL server fill in these defaults.

Thanks!
-f!

Title: Great Article !!!
Name: Jash
Date: 2009-04-13 3:24:14 PM
Comment:
Thank you Brian really useful article.