Blog Home  Home Feed your aggregator (RSS 2.0)  
What did you learn today? - Research and Development Progress - Stuck
Phil Denoncourt's Technology Rants
 
 Monday, November 12, 2007

I'm retrieving data without effort now.  The Linq syntax is starting to sink in.  I don't have to look at the reference as much anymore.  I think I'm stuck, though.  I'm trying to send updates back and I was hoping to have one method per entity called "Save" that would take in the modified entities and use Linq magic to get it back to the database.  No such magic seems to exist.  I'm going to have to write a method per operation (Delete, Insert, Update).  What stinks is that the work required to do this is about the same as it was before using traditional methods.

This could be a case of programming in a closet and not having anyone currently present to bounce ideas off of.  I'm going to bounce this off some of the developers when I go back to work tomorrow.

So far, Linq has a nice intuitive syntax and allows a standardized way of querying collections.  It's also nice that it supports lazy loading and relationships natively. However, from a productivity point of view, I'm not sure it adds a lot to what we currently have. 

Monday, November 12, 2007 8:15:10 PM (GMT Standard Time, UTC+00:00)  #    Comments [1]    | 
Wednesday, November 21, 2007 2:11:07 PM (GMT Standard Time, UTC+00:00)
Phil,

I think what you are looking to do is already there for you. LINQ supports persisting changes made to your objects.

All changes to the objects are maintained and can be written back to the database on demand using the submitChanges() method.

Is this what you are looking to do or did I misunderstand your question??

Mike
Michael Flanagan
Comments are closed.
Copyright © 2008 Phil Denoncourt III. All rights reserved.
DasBlog 'Portal' theme by Johnny Hughes.
Pick a theme: