DevForce Community Forum : Asynchronous cascading deletes http://www.ideablade.com/forum/ This is an XML content feed of; DevForce Community Forum : DevForce 2010 : Asynchronous cascading deletes Sun, 12 Apr 2026 13:46:05 -700 Mon, 01 Nov 2010 00:43:40 -700 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 9.69 360 www.ideablade.com/forum/RSS_post_feed.asp?TID=2178 DevForce Community Forum http://www.ideablade.com/forum/forum_images/IdeaBlade_logo_tm.png http://www.ideablade.com/forum/ Asynchronous cascading deletes : Aah, that makes sense. I also... http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8992#8992 Author: pompomJuice
Subject: 2178
Posted: 01-Nov-2010 at 12:43am

Aah, that makes sense.

 

I also was referring to a slightly different situation.

 

My issue was that if I delete an entity and it happens to have a 1..* NOT NULL parent child relationship with another entity that is set to cascade in the database. Such a delete is not possible unless you remove the 1..* loaded children from devforce, otherwise it deletes the parent and updates the children's FKs to NULL which causes FK exceptions.

 

Hope that makes more sense. ( And saw nothing on this topic in the documentation either? The documentation is very quiet about cascading deletes. )

 

Personally I was hoping that devforce could see that a cascade is set via EF 4.0 and compensate. I was over optimistic.

]]> Mon, 01 Nov 2010 00:43:40 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8992#8992 Asynchronous cascading deletes : pompomJuice, The suggestion... http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8976#8976 Author: sbelini
Subject: 2178
Posted: 29-Oct-2010 at 9:41am

pompomJuice,
 
The suggestion I provided is for deleting all entities via DevForce.
Of course you can set the cascading delete in your Database and save the wire traffic.
 
Sorry for the confusion.
 
Silvio.
]]> Fri, 29 Oct 2010 09:41:25 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8976#8976 Asynchronous cascading deletes : Indeed there is. Drop any potential... http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8974#8974 Author: pompomJuice
Subject: 2178
Posted: 29-Oct-2010 at 7:08am

Indeed there is.
 
Drop any potential cascade deletes from the Entity Manager's cache and then delete the entity, the database will take care of the rest. That way the EM wont fail on those updates. Makes sense.
]]> Fri, 29 Oct 2010 07:08:36 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8974#8974 Asynchronous cascading deletes : That is ridiculous. You fetch... http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8972#8972 Author: pompomJuice
Subject: 2178
Posted: 29-Oct-2010 at 5:41am

That is ridiculous.
 
You fetch entities to delete them.  What if you want to delete an entity that contains 100 images? (my situation)
 
There has to be a better way?
 
]]> Fri, 29 Oct 2010 05:41:55 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8972#8972 Asynchronous cascading deletes : The simplest way would be pre-loading... http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8600#8600 Author: sbelini
Subject: 2178
Posted: 22-Sep-2010 at 2:35pm

 
The simplest way would be pre-loading all dependent objects and then deleting.
 
You could also have it executed on the server (i.e. calling InvokeServerMethod).
 
The example in the post you mentioned still works on DevForce2010 (only a slight minor change needed - AsyncCompletedCallback<> is not present in DevForce2010):
 
 
  AsyncSerialTask.Create<Customer>("DeleteCustomer")
    .AddAsyncAction<AsyncEventArgs>(SetupDeletion)
    .AddAction(args => DoDelete((Customer)args.UserState))
    .Execute(aCustomerToBeDeleted);
 
  private void SetupDeletion(Customer cust, Action<AsyncEventArgs> callback) {
    var list = cust.Orders;
    bool isPending = list.IsPendingEntityList;
    if (isPending) {
      list.PendingEntityListResolved += (o, args) => {
        callback(new AsyncEventArgs(cust));
      };
    } else {
      callback(new AsyncEventArgs(cust));
    }
  }
 
  private void DoDelete(Customer cust) {
    cust.EntityAspect.Delete();
    foreach (var order in cust.Orders.ToList()) {
      order.EntityAspect.Delete();
    }
  }
 
 
]]> Wed, 22 Sep 2010 14:35:59 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8600#8600 Asynchronous cascading deletes : What is the current recommended... http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8587#8587 Author: kpozin
Subject: 2178
Posted: 21-Sep-2010 at 1:25pm

What is the current recommended method for managing asynchronous cascading deletes in Silverlight?

Has this issue in DevForce 2009 been fixed?
]]> Tue, 21 Sep 2010 13:25:10 -700 http://www.ideablade.com/forum/forum_posts.asp?TID=2178&PID=8587#8587