Add into_model() for Insert/Update/Delete

[nicoulaj]

It is a common need to insert/update/delete and select some return columns as a single query. Currently sea-orm does not make this easy, so I think having ideally into_model() for Insert/Update/Delete would be very convenient. What do you think ?

[nicoulaj]

related: SeaQL/sea-query#120

[billy1624]

1. I'm thinking how we handle databases that don't support returning? Should we just return the original ActiveModel passed into insert / update / delete?

2. Also, what will be returned if we insert / update / delete multiple records? Or this into_model() method is not supported for insert / update / delete multiple records.

[nicoulaj]

I'm thinking how we handle databases that don't support returning? Should we just return the original ActiveModel passed into insert / update / delete?

Indeed, it looks like this is supported by postgres, sqlite and mariadb but not mysql... Maybe use a feature flag ?

Also, what will be returned if we insert / update / delete multiple records? Or this into_model() method is not supported for insert / update / delete multiple records.

I don't see how this is different from normal select ? into_model() returns a Selector, Selector::all() returns a Vec. But maybe I am missing something.

[marlon-sousa]

Hello,

Can you post a pseldo_code to demonstrate how this should work?

I am interested in the api level, not in implementations.

For me, ideally, insert_many and update_many should always return a compound struct with number of affected rows and a vec of returned records, containg activemodel with the columns the querier asked for or an empty vector otherwise.

This would be the clearer way to let everyone to know what is going on in a way that is not so magical that is not intuitive unless you know the framework and is not so low level that makes code umreadable from the user point of view.

[tqwewe]

Is this related?
#240

[nicoulaj]

I think this issue can be closed since #183 handled it ?

[billy1624]

Ty!