mohs8421

these elements are defined in types, where I would expect complex types to be defined, not elements of complex types

Current output is something like this: ```xml ``` I removed a lot of duplicates and unimportant details for you, just imagine, that this filter_arr example is used by many operations...

That approach actually matches pretty good with a part of what I did before to get the "full" record. That means not only have the changed record I get from...

The snippet is intended to put the two pieces together. Let's say I get an active model from my frontend, and match that with the model as it is in...

Please note the `T::from_json(…)` part, where I already use what you suggested.

@teenjuna take a look at https://github.com/SeaQL/sea-orm/blob/master/src/entity/active_model.rs#L281 as an example, there you would only need to pass C into the behavior and similar things would need to be done in the...

I decided for this route to not loose any information on the original sqlx error in case it is not a database error. But honestly I'm not even sure that...

@billy1624 it is a little more complicated than that. I want to consume the error, if it is a database_error, but not in other cases. Now `as_database_error` will never consume...

> Hey thank you for your effort. I have a slightly different idea to the implementation, might need @billy1624 's help indeed. would you care to elaborate, what your idea...

The important question here is: What would the user of sea-orm want in the case of an error? The users usually want to know, whether they can circumvent this error...