Why insert, update, etc return a ActiveModel instead of Model?

[edg-l]

I find it curious, since you can easily go from a model to a activemodel, but not backwards (from what i've seen), and most of the time after a insert i want the Model which i can return from my api.

I've seen the impl of the insert model and it in fact does a query to find the inserted model and then it converts it to a activemodel, I think we should let the end user decide whether to convert it to a activemodel or not and just return a model.

[tyt2y3]

You have made a good point! I agree that the conversion could seem unnecessary.

For now, the returned object of 'update' is the input ActiveModel.

So may be it makes sense that the return type of 'model.insert()' is Self.

And they also trigger the ActiveModelBehavior

Do you have new thoughts on it?

[Paul-Vandell]

+1 here. So finally we have to make a double select query to get back the last inserted user as Model finally right ? related to #148

[tyt2y3]

Thanks for the input. We thought about it, and our plan for now is to introduce a InsertModel::insert() method that does not involve ActiveModel; same applies to UpdateModel::update().