StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11120912
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-20T13:40:18.327
FavoriteCount
0
LastActivityDate
2012-06-20T14:14:24.067
LastEditDate
2012-06-20T14:14:24.067
LastEditorUserId
540345
OwnerUserId
540345
ParentId
11120335
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
The <code>DataContext</code> should always be short-lived. You should re-factor your design to achieve this. You can consider these points: <ul> <li>Use context per transaction. This way you can make the context short-lived in meaningful way.</li> <li>Rollback when your transaction fails. This includes inserting correct item with new transaction. That means, you have a fresh different context now.</li> <li>Repeat the process until the transaction completes.</li> <li>Again, don't forget to end the context when you are done. This can be easily achieved by making use of the <code>using</code> statement.</li> </ul> <a href="http://msdn.microsoft.com/en-us/library/system.data.linq.datacontext.aspx" rel="nofollow">Remark from MSDN</a>: <blockquote> The DataContext is the source of all entities mapped over a database connection. It tracks changes that you made to all retrieved entities and maintains an "identity cache" that guarantees that entities retrieved more than one time are represented by using the same object instance. In general, a DataContext instance is designed to last for one "unit of work" however your application defines that term. A DataContext is lightweight and is not expensive to create. A typical LINQ to SQL application creates DataContext instances at method scope or as a member of short-lived classes that represent a logical set of related database operations. </blockquote> <hr> If it takes time to re-factor your design, temporarily you can do like this: <pre><code> public void InsertList(List<Person> people) { foreach (var person in people) { DoInsert(person); // You can use the returned flag and implement the logic if desired. // Or let the loop move on its ways. } } public bool DoInsert(Person person) { try { using (DataModelDataContext dataContext = new DataModelDataContext()) { dataContext.Persons.InsertOnSubmit(person); dataContext.SubmitChanges(); } return true; } catch (Exception ex) { Console.WriteLine(ex.Message); return false; } } </code></pre> and this is how you can call <code>InserList</code> Method: <pre><code> List<Person> liste = new List<Person>(); liste.Add(new Person { FirstName = "AAA", LastName = "BBBB" }); liste.Add(new Person { FirstName = string.Empty, LastName = null }); liste.Add(new Person { FirstName = "CCC", LastName = "DDD" }); InsertList(liste); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POLinq2SQL, use dataContext after Exception
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNaveenBhat
UserOwnerUserId
1. USNaveenBhat
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POLinq2SQL, use dataContext after Exception
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.