TYPO3 Core

DBAL could parse the query for the & operator.

OTOH as & is perhaps rarely used it could XLCASS the function in the Core which uses the & and use BITAND for Oracle.

The incompatible code is made by t3lib_userAuthGroup.getPagePermsClause().

Unfortunately, changing the code there to "BITAND" causes the dbal to refuse the translation of the statement.

IMHO either the way of getting user's permission or the capabilities of the dbal to handle bitwise operators have to be changed.

Is there any workarround for this bug? Or does it need more information or investigation? we have exact the same issue on a ORACLE 10G 10.1.0.4.2 Database

We have the same pb on Oracle Database 10g Release 2 (10.2.0.1.0) under Linux . Can we hope for a corrective measure asap?

thanks a lot for this great CMS.

Hi,

We wish use this cms in our entreprise, but we can't choose this one whith this major bug.

We have to let the project in stand-bye, waiting this fix.

Cordially.

Y.V.

Karsten, didn't you have a workaround (if not a fix) in a planning state, or so?

is there any workaround to solve problem?

Fixed in SVN.

Those interested please check out the DBAL extension from TYPO3 SVN trunk and check if ot helps. Mind that it might be best to recreate all tables, as longer text fields are CLOB fields now, as well.