Urban Suppiger

If I understood correctly, @carlobeltrame was working on the idea on how to specify serialization groups via request, which controls what data will be embedded in the response. However, the...

Trying to further pinpoint on this, I believe the issue comes form the OnetoOne-Relation between `AbstractContentNodeOwner->rootContentNode` and `ContentNode->owner`. The additional queries are triggered by the same code line here: https://github.com/doctrine/orm/issues/2239#issuecomment-162357902...

> If the target-entity of a many-to-one or one-to-one association is a CTI entity, it is preferable for performance reasons that it be a leaf entity in the inheritance hierarchy,...

Other options: - Try disable eager loading (https://api-platform.com/docs/core/performance/#force-eager)

Trying to dig a bit further down the rabbit hole. As to my current understanding, the following examples could lead to additional SQL-queries and therefore to a potential performance problem....

As discussed try to make option 1 mergeable with following changes: - Remove owner property - Don't store camp redundantly on ContentNode - Implement new Voter for security checks of...

> So for you [usu#7](https://github.com/usu/ecamp3/pull/7) is not an option? [usu#7](https://github.com/usu/ecamp3/pull/7) oder ähnlich wäre für mich das Minimum. Der Vorschlag hier geht halt ein gutes Stück weiter mit verschiedenen Pros/Cons. Wahrscheinlich...

Current state of affairs: https://github.com/usu/ecamp3/pull/8 (still very experimental)

Implemented in #2825

Approach described below could potentially work: https://github.com/json-schema-org/community/discussions/150