Re: Should TList<Entity> Save in EntityProviderBaseCore use three seperate steps for Delete, Update and Insert?

Hi Doug.

I am new to Codesmith and NetTiers and am running into the same problem described in your post. 

Separating and changing the order of events seems the best way to solve the problem.  The proposed method change looks good from my point of view.  An additional post on the topic also supports the proposed order of execution. http://community.codesmithtools.com/forums/p/3037/12603.aspx#12603

Does anyone else have any thoughts?  How do we go about submitting the proposal as a change candidate for the next release?

The change has worked out great, I have not had any problems with it (yet).

I have not looked into submitting a patch, but after looking at http://community.codesmithtools.com/forums/t/3450.aspx I will try to submit something in the next couple of weeks.

 Doug

There is an additional change required in the internal method EntityProviderBaseCore.DeepSave.  Replace the two existing foreach loops for DeepSaving with the code below.  It follows the same logic as the original code you posted.

foreach (Entity entity in entities)
{
  if (!entity.IsNew)
  {
    result = DeepSave(mgr, entity, deepSaveType, childTypes, innerList);
    if (!result)
    {
      deepSaveResult = false;
    }
  }
}

foreach (Entity entity in entities)
{
  if (entity.IsNew)
  {
    result = DeepSave(mgr, entity, deepSaveType, childTypes, innerList);
    if (!result)
    {
      deepSaveResult = false;
    }
  }
}

I have overridden both methods with the new implementations and will be testing over the next week or so.  Then I presume it would be time for a patch submission.

Thanks Doug.

Daniel

Oh man, I had missed that method.

Thanks!

Doug