Bug #17235
closed
Sorry, you didn't have proper permissions to perform this change.
0%
Description
The above mentioned error occurs on trying to create any kind of record. (pages, contentelement, tt_news etc.)
When having set :
$TYPO3_CONF_VARS['EXTCONF']['dbal']['handlerCfg'] = array (
'_DEFAULT' => array (
'type' => 'native',
'config' => array (
'username' => '', // Set by default (overridden)
'password' => '', // Set by default (overridden)
'host' => '', // Set by default (overridden)
'database' => ''
)
),
);
$TYPO3_CONF_VARS['EXTCONF']['dbal']['debugOptions'] = array(
'enabled' => TRUE,
'printErrors' => TRUE,
'EXPLAIN' => 1,
'parseQuery' => 1,
'joinTables' => 1
);
removing debugOptions makes the problem disappear.
typo3 4.1.1
ADOdb adodb 4.94.0
Database Abstraction Layer dbal 0.9.9
(issue imported from #M5485)
Updated by Martin Kutschker about 17 years ago
I had not this problem, but enabling the DEBUG options got me lot of SQL errors on Oracle.
Updated by Karsten Dambekalns about 17 years ago
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?
Updated by Marc Bastian Heinrichs about 17 years ago
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
Updated by Ernesto Baschny almost 17 years ago
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).
Updated by hans about 16 years ago
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)
Updated by Michael Miousse over 15 years ago
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
Updated by Michael Miousse over 15 years ago
is this bug only on native or on other type of db too?
Updated by Xavier Perseguers over 14 years ago
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....)
Updated by Alexander Opitz over 10 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0) - TYPO3 Version set to 4.1
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz over 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.