Should objects in ORM contain operations other than CRUD?

Usually, the User class would extend an ORM class that provides the standard CRUD interface. The additional functions you talk about would very well fit within the User class itself.

Usually, the User class would extend an ORM class that provides the standard CRUD interface. The additional functions you talk about would very well fit within the User class itself. It is always good practice to make 'fat models' and skinny controllers, i.e.

Put all logic that is directly related to data manipulation in the models, and only the 'overarching' logic in the controllers. See e.g. Here for more info weblog.jamisbuck.org/2006/10/18/skinny-c....

In my most favorite framework (Kohana), we have: ORM::factory('user')->where()->find_all(); and the corresponding delete() (replacing find_all() above). Are you writing your own ORM library? If yes, then you can make operations that deal with more than one record as class methods instead of instance methods.It's up to your design, however.

Kohana, for instance, still make it instance method.

It depends on how you architecture your ORM solution. My approach would be to enclose collective actions (made on multiple records at once) into some class representing eg. Database table storing users or the one responsible for the basic ORM actions - depending whether they are table-specific or not.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.