TYPO3 Core

Actually this has impact on all kinds of relations to the same model, different example:
query->equals('parent.gender','male');

would result in
select * from person left join person on person.parent = person.uid where person.gender = 'male'

instead of
select * from person left join person as parent on person.parent = parent.uid where parent.gender = 'male'

Is this feature planned for 6.2 release?! We have huge problems because we cannot make custom queries with subclasses of the same type (table)!

I think there are three workarounds:

• we have to build a second table, which have the same structure as the table of the subclass -> prevents alias problem

• we have to make multiple custom queries
  • first search the subclass table
  • second search the parentclass table with "$query->in(...)"
    -> for many records this leads to a big performance problem, because in the first query many results will be possibly instantiated

• we should use this patch
  • not good, because we dont know what the side-effects are

I will try the first solution (its overhead but i hope it works!)

The attached file is not working very well but having multiple tables sounds like a very bad solution.

I think its absolutely possible to use an alias. you just have to use the property path as key and generate an alias if neccessary (if table has been joined on a different propertypath allready or the root table is the same).

I think its not so much work! You just have to move the while construct, that generates the joins in a method, there you could work with a register.

I set target version to 6.2 because i see this as extbase core functionallity, subclassing and domain model inheritance is possible, so this has to be possible too.

Sadly i dont find time besides my regular work to provide a solution.

Are there any news on this? We are planning a new version (for cms 7) of some big extension we developed and now we have to dicide if using the domain model inheritence is still an option.

Please send some feedback if any work/planning has taken place here.

thank you.

Is this solved now?

27057

https://forge.typo3.org/projects/typo3cms-core/repository/revisions/755a948bea34d2269dc77720d37091bba5105a0b

When do you plan to fix this issue??

André Wuttig wrote:

When do you plan to fix this issue??

When someone confirms that it was already fixed with #27057. :-)