http://blogs.msdn.com/b/alexj/archive/2009/06/05/ordering-of-commands-what-do-you-think.aspxSome of our customers write code like this: ctx.AddToCustomers(customer); ctx.AddToProducts(product1); ctx.AddToProducts(product2); And expect the Entity Framework to issue 3 insert commands in the same order. Today the EF doesn’t preserve this sort ofen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/alexj/archive/2009/06/05/ordering-of-commands-what-do-you-think.aspx#9707713Mon, 08 Jun 2009 11:31:29 GMT91d46819-8472-40ad-a661-2c78acb4018c:9707713DaveR<p>Can't think of a single reason why ordering would be important. &nbsp;EF is a way of hiding the complexities of the storage mechanism, so why would I want to use EF if I have specific storage-mechanism requirements?</p> <p>FWIW I think you're right to not bother preserving order.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9707713" width="1" height="1">http://blogs.msdn.com/b/alexj/archive/2009/06/05/ordering-of-commands-what-do-you-think.aspx#9702892Sat, 06 Jun 2009 19:10:43 GMT91d46819-8472-40ad-a661-2c78acb4018c:9702892Alex D James<p>Thanks for the feedback Vijay</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9702892" width="1" height="1">http://blogs.msdn.com/b/alexj/archive/2009/06/05/ordering-of-commands-what-do-you-think.aspx#9702325Sat, 06 Jun 2009 03:06:22 GMT91d46819-8472-40ad-a661-2c78acb4018c:9702325Vijay<p>we need ordering!!</p> <p>Keep it simple.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9702325" width="1" height="1">http://blogs.msdn.com/b/alexj/archive/2009/06/05/ordering-of-commands-what-do-you-think.aspx#9701851Fri, 05 Jun 2009 22:33:52 GMT91d46819-8472-40ad-a661-2c78acb4018c:9701851Alex D James<p>Wojciech,</p> <p>I like your obj1.DependsOn(obj2) idea.</p> <p>very interesting</p> <p>Alex</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9701851" width="1" height="1">http://blogs.msdn.com/b/alexj/archive/2009/06/05/ordering-of-commands-what-do-you-think.aspx#9701829Fri, 05 Jun 2009 22:28:08 GMT91d46819-8472-40ad-a661-2c78acb4018c:9701829Wojciech Gebczyk<p>Hmm... The only &quot;resonable&quot; reason that defining object dependency would be valuable is when there are constraints on DB that cannot be expressed in EDMX because of some reasons (partial mapping? procedures? triggers?). In such case having method on object/context like obj1.DependsOn(obj2) will be sufficient.</p> <p>IMHO...</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9701829" width="1" height="1">