Have a look at the Attach() method and friends. On Tue, Apr 21, 2009 at 17:01, <[email protected]> wrote:
> > Hi All, > > I'm sure this has been answered before so sorry in advance, I couldn't > discover the answer. > > I have some objects (or entities as now seems to be the description) > that I load with DBLinq. I serialise those objects up over WCF and > send them down to a client which will send back the standard add, > update and delete requests. Add and delete are ok but I'm a bit lost > about how to do the updates with DBLinq? > > I understand the INotifyPropertyChanged concept but in my case the > client could have changed a whole lot of properties and I'd like to > update the database with the property values the client has sent. I'm > not too concerned about which properties have changed I'd like them > all to be updated every time the client sends any update request. > > I've used the Attach method but it fails more often than not and I'm > assuming that's because the object is already in the table. How do I > update or replace the object in a table with one the client has sent > to me and then force DBLinq to update that object into the database? > > Thanks, > > Greyman. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
