Well here's the thing, I think.
If I take edit out of employee, then some other system needs to have edit.
And if another system needs to have edit, it needs to know how to edit whatever we give it (what if it's not an employee?)
I could use polymorphism and create a class called database_object, and virtualize member functions like edit.
I can't think of a real clean way to handle the edit function being in another class. Ultimately I would want that system to handle more than just an employee object.