TYPO3 Core

Basicly, this is a regression, introduced by fix of #60613.

A more detailed description:

This commit changes behavior of query selection.

Was
Either records from requested language or non-translated records are fetched.

Now
Either records from requested language or non-translated to requested language records are fetched.

So far so good, until we use ->setLimit() in queryBuilder and config.sys_language_mode = strict in TS.

Real life example: we have a lazy-loading feature on a website, where records are loaded by portions of 6. Six records are shown and when user scrolls the window down, next 6 are requested and so on. We don't have any language fallbacks and always show records from requested language (config.sys_language_mode = strict).
With TYPO3 6.1.10 this was working like a charm, but with TYPO3 6.1.11 it broke, because now all the records, that are not translated, are fetched as well, but later they are cut down by doLanguageAndWorkspaceOverlay(), so instead of 6 records, only 2 are shown (sure, this number may vary between 0 and 6).

This is treated as major bug, which blocks us from further 6.1 updates, and I assume will block us on 6.2.4 as well, since same fix was applied to 6.2.5.

More side notes: in commit notes following is written:
Currently when TYPO3 is configured to do language fallback
and a record is translated in language A, but not
in language B and language B is requested, then this
record is excluded.
But this is not really truth. In our case we don't have any language fallback and that huge $additionalWhereClause in addSysLanguageStatement() is added by checking following condition:

if (isset($GLOBALS['TCA'][$tableName]['ctrl']['transOrigPointerField'])
    && $querySettings->getSysLanguageUid() > 0
)

If a TCA has 'transOrigPointerField' and requested language is not 0, then we add something, like: OR (tx_record.sys_language_uid=0 AND tx_record.uid NOT IN (SELECT tx_record.l10n_parent FROM tx_record WHERE tx_record.l10n_parent>0 AND tx_record.sys_language_uid=2 AND tx_record.deleted=0)))
As you can see, it has nothing to do with "TYPO3 is configured to do language fallback", but with TCA field, which exists for almost any table.

To be honest, even TYPO3 6.1.10 is affected by this, but probability of this bug to appear is much lower: record needs to exist in default language only (has no translations) - then the record will be fetched as well. And in my example above doLanguageAndWorkspaceOverlay() will cut it down.

Possible fixes:
1. (fast and dirty) revert fix of #60613.
2. change condition:

if (isset($GLOBALS['TCA'][$tableName]['ctrl']['transOrigPointerField'])
    && $querySettings->getSysLanguageUid() > 0
)

to:

if (isset($GLOBALS['TCA'][$tableName]['ctrl']['transOrigPointerField'])
    && $querySettings->getSysLanguageUid() > 0
    && $GLOBALS['TSFE']->sys_language_mode != 'strict'
)

TYPO3 6.1.11