TYPO3 Core

The problem has been reproduced by me, reason is the use of table aliases in this case. While this works to some extent, it breaks here. I fix is not yet available.

Can also be reproduced using typo3 4.1.1 with MySQL as DB. Exactly the same error message as shown above:

DBAL fatal error: No handler found in handler_getFromTableList() for: "(be_sessions, be_users u) LEFT OUTER JOIN be_users bu ON (ses_backuserid=bu.uid)" (SQL engine parse ERROR: No table name found as expected in parseFromTables()!: near "(be_sessions, be_users u) LEFT OUTER JOIN be_users")

That means the summary should probably not contain postgresql cause it's obviously not a database related problem, rather sql related.

Same happens to me when BE > User Admin > List Users Online
typo3 4.1.1 & mysql

DBAL fatal error: No handler found in handler_getFromTableList() for: "(be_sessions, be_users u) LEFT OUTER JOIN be_users bu ON (ses_backuserid=bu.uid)" (SQL engine parse ERROR: No table name found as expected in parseFromTables()!: near "(be_sessions, be_users u) LEFT OUTER JOIN be_users")

Same happens to me when BE > User Admin > List Users Online
typo3 4.1.1 & mysql

DBAL fatal error: No handler found in handler_getFromTableList() for: "(be_sessions, be_users u) LEFT OUTER JOIN be_users bu ON (ses_backuserid=bu.uid)" (SQL engine parse ERROR: No table name found as expected in parseFromTables()!: near "(be_sessions, be_users u) LEFT OUTER JOIN be_users")

patch fixes the issue in be module for mysql

thanks, for the Patch it works fine...
--------------
i had this problem on:
openSuSE 10.1
php5.1.2
mysql 5.0.18
Typo3 4.1.0 & 4.1.2 & 4.1.3
AND
Debian Etch amd64
php5.2.4-1 (compiled)
MySQL 5.0.32-Debian_7etch1-log
Typo3 4.1.3

The path removes the brackets around (be_sessions, be_users u). Does the patch work with them? There was a reason for them which I cannt recall right now.

Could you please test whether patch for bug #21147 solves this issue too? If so, please close this bug and patch 12071.diff does not change the query itself but solves the SQL parser bug itself.

Fixed with patch provided on bug #19073. Please acknowledge on Core list. Thanks.

Commited to trunk, rev.6315 (4.3 beta3)