Recent "fixes" in t3lib_loaddbgroup introduces potentially hard found bugs in 3rd party applications
The internal variable ->itemArray in t3lib_loaddbgroup doesn't use numerical keys that indicates order of elements. The key is now a string, being a combination of table and uid.
This introduces the following problems:
- Applications like sys_refindex (core), TemplaVoila (external!) are using the key as sorting key (0,1,2...) etc. We can't know how many other applications are relying on this (for years!)
- Using table_uid will disallow duplicate entries in the array - an obvious feature of TYPO3!!!
- The implementation is probably buggy; in function readList() values are put into $this->itemArray[$itemKey] and $this->itemArray[$key] suggesting an incomplete implementation.
I would like this reverted immediately or otherwise be presented for compelling evidence why this is necessary!
I would also like to know how Rene will defend that a (de facto) "public API" like ->itemArray should change so radically.
(issue imported from #M2932)