Save me on a business object

Question

I usually saw such examples on business objects:

public void Save()
{
     if(this.id > 0)
     {
          ThingyRepository.UpdateThingy(this);
     }
     else
     {
          int id = 0;
          ThingyRepository.AddThingy(this, out id);
          this.id = id;
     }
}

So why here at a business facility? This is more like context or data related more than business logic.

For example, the consumer of this object can go through something like this ...

...Get form values from a web app...

Thingy thingy = Thingy.CreateNew(Form["name"].Value, Form["gadget"].Value, Form["process"].Value);
thingy.Save();

Or something like this to update ...

... Get form values from a web app...

Thingy thingy = Thingy.GetThingyByID(Int32.Parse(Form["id"].Value));
Thingy.Name = Form["name"].Value;
Thingy.Save();

So why is that? Why not contain the actual business logic, such as calculations, business rules, etc., And avoid searching / saving?

Using this approach, the code might look like this:

... Get form values from a web app...

Thingy thingy = Thingy.CreateNew(Form["name"].Value, Form["gadget"].Value, Form["process"].Value);
ThingyRepository.AddThingy(ref thingy, out id);

Or something like this to update ...

... get form values from a web app ...

Thingy thingy = ThingyRepository.GetThingyByID(Int32.Parse(Form["id"].Value));
thingy.Name = Form["Name"].Value;
ThingyRepository.UpdateThingy(ref thingy);

In both examples, the consumer who knows best what is being done with the object calls the repository and either requests ADD or UPDATE. An object remains a DUMB in this context, but still provides it with basic business logic pertaining to itself, and not how it is retrieved or stored.

, GET SAVE -.

, - ?

Answer 1

(. P of EAA . 160).

. - , -? ? ? - Account, Account.Save, Account.Find? Yucky.

, . , , , , /, .., .

Answer 2

.

, persistance, ( ).

, ( , ), - . , .

Answer 3

DDD, 1 ( UPSERT. , , ).

"" "" . .

EDIT: , INSERT UPDATE, . Repository.Save(....), ( ) .

Answer 4

If you do not like what their approach makes your own. Personally, Save () instance methods on business object objects are really good for me. Another class name that I need to remember. However, I have no problem saving the factory, but I don’t understand why it would be so difficult to have both. IE

class myObject
{
   public Save()
   {
      myObjFactory.Save(this);
   }
}
...

class myObjectFactory
{
   public void Save(myObject obj)
   {
      // Upsert myObject   
   }
}