TYPO3 Core

I had not this problem, but enabling the DEBUG options got me lot of SQL errors on Oracle.

Nikolas, could you please check exactly which if the debug options causes this? I.e. enable them one by one and see if it breaks?

Hi Karsten,

the enabled option causes the problem. The sys_log shows an error, that the content element couldn't be inserted on the root level. But in spite of the errors in the BE and sys_log, the ce was inserted on the right page.

greets
marc bastian

Well, I just went into the same trouble today and had DBAL + debug enabled, which caused exactly the problems which are reported here and which are explained in more detail in #0005810.

When creating any new record (e.g. tt_content), hitting "save" to save + reload the edit form for the new record, typo3 tries to makeEditForm() for the correct table but for a totally wrong UID: now the last_insert_id from the tx_dbal_debuglog table instead from my originally being edited table.

Solution would be as proposed by Marcel Gsteiger in other bug report: either user another mysql link for debug output or handle last_update_id different if debugging is enabled. I would favor the first choice, as other stuff might get scrambled if we use the same mysql link for normal operations and for "debugging" (mysql_error, last executed query, etc).

I have the same error. When i set $TYPO3_CONF_VARS['EXTCONF']['dbal']['debugOptions'] = array('enabled' => FALSE, ...), it works fine.

Typo3: v4.1.3
Database: DBAL _DEFAULT to MySQL (type: native) and a extended connection to a MS-Access DB (type: adodb, driver: access)

either user another mysql link for debug output or handle last_update_id
ok maybe but what should i do with pconnect? i cant create 2 different connection to the same database if pconnect is used.

so the bottom line is that we can't open a second connection unless we create a new user for debug only in our bds.

the other solution would be to do the same as queries with adodb and store last_inserted_id just after the insert and return this variable when sql_insert_id is called

is this bug only on native or on other type of db too?

This happens on an Oracle database when a field has changed its type from mediumtext to mediumblob for instance (typically appears with recent changes in the different tables with TYPO3 4.3.0) as there is an underlying error:

SQL error: 'ORA-00932: inconsistent datatypes: expected BLOB got CLOB' (tt_content:NEW....)