Feature #8462
Check subobjects in query rewriting
| Status: | New | Start date: | 2010-06-23 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | Security | |||
| Target version: | - | |||
| PHP Version: | Complexity: | |||
| Has patch: |
Description
For usual queries this could be done by adding join conditions. For an object retrieved by UUID this has to be discussed.
History
#1 Updated by Karsten Dambekalns about 5 years ago
When we introduce this we need to make sure we do not delete stuff that was kept from being visible. Currently the danger is in the use of removeProperties() within setProperties()...
#2 Updated by Andreas Förthner about 5 years ago
With the current persistence backend implementation this is not needed. But as soon as the backend optimizes queries to fetch more than one object at a time, we will have to intercept the query optimization and add the needed constraints for all fetched subobjects.