Multiple find_with_related()

[Kijewski]

Let's say I have a parent::Entity with zero or many good_child::Entity, neutral_child::Entity, and chaotic_child::Entity. (Just an example. The actual child_* tables have nothing in common with one another).

Each child has a field with its parent's id. Now I can select all good_children for some parent with

let (parent, good_children) = model::parent::Entity::find_by_id(42)
    .find_with_related(model::good_child::Entity)
    .all(&db.begin().await.map_err(…)?)
    .await
    .map_err(…)?
    .pop()
    .ok_or(…)?;

But how can I get the neutral and chaotic children in the same query? Simply adding another find_with_related() call does not work:

no method named find_with_related found for struct SelectTwoMany in the current scope

method not found in SelectTwoMany<…::parent::Entity, projektdb_model::good_child::Entity>

---

I asked the same question on stackoverflow, too: Multiple find_with_related() in sea_orm. I hope that's not too much noise.

[billy1624]

Hey @Kijewski, sorry for the delay. Currently we only support one *_related at a time. So, I'd suggest you to create a custom struct to hold the query result of each row consist of good_child, neutral_child and chaotic_child data. See https://www.sea-ql.org/SeaORM/docs/advanced-query/custom-select/#handling-custom-selects for details.

[Kijewski]

Thank you for your answer! I feared something like that was necessary. :) But well, it could be worse.

Thank you for the project! This was until now the only problem I had.

[ChoaibMouhrach]

@billy1624 is this feature added ?

[cnwzhu]

A typical query usually involves joining several tables, but the current functionality is difficult to use.

[JoelGarcia99]

Any update on this? Is this feature coming in the future?

[Reinhard-Berger]

Would be a Great feature

[cnwzhu]

Not only does find_also_related need to be called multiple times, but find_with_related, find_also_linked, and find_with_linked should also be able to be called multiple times. I don’t quite understand why the default design was set to relate to only one table in the query. If it can relate to one, why can’t it relate to multiple? It’s so strange. A typical query usually involves joining several tables, but the current functionality is difficult to use.