Project

General

Profile

Actions

Bug #16952

closed

Calling "DB Check" -> "Record Statistics" results in many SQL-related errors

Added by Christian Brunner almost 18 years ago. Updated over 17 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2007-02-07
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.1
PHP Version:
5
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When I call "DB Check" -> "Record Statistics" I get a lot of errors in t3lib/class.t3lib_db.php in lines around 800.

Reason:
The functions "sql_fetch_assoc()" and "sql_fetch_row()" don't check, whether $res is a valid SQL Resource

I got these warnings on PHP Error Level E_ALL

I attached a diff-file that fixed the problem for me

I think this also affects Version 4.0.4 but i'm not sure

MySQL 5.0.22
(issue imported from #M4939)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #16961: Sql Error editing BE UserClosedMichael Stucki2007-02-09

Actions
Actions #1

Updated by Christian Brunner almost 18 years ago

I forgot to say that I got this error with 4.1RC1 but I could only select 4.1beta3...
sorry for that

Actions #2

Updated by Michael Stucki almost 18 years ago

Did you update the database in the Install Tool?

Actions #3

Updated by Christian Brunner almost 18 years ago

yes
today i
1) changed the sources form 4.0.4 to 4.1RC1
2) made a DB update
3) changed the compatibility mode to 4.1

=> error was still there
btw: the error was already there with 4.0.4 (clean install)

Actions #4

Updated by Christian Brunner almost 18 years ago

@anyone looking at this bug:

PLEASE DONT USE THE PATCH!!!! (i cant delete it)
the patch just supresses the error but doesn't solve it!

the problem seems to be "deeper" (look at bug 0004951)

[EDIT] it was an mysql bug (i think in 5.0.22) -> update mysql and it works just fine

Actions #5

Updated by Oliver Hader almost 18 years ago

The error depends on MySQL 5.0.22 which is unable to handle query parts like "... IN (-1,0,123) ..." (negative integer and positive integer in an "IN (...)" statement).
The error was fixed in MySQL 5.0.23/5.0.24, see http://bugs.mysql.com/bug.php?id=19618.

Actions #6

Updated by Michael Stucki almost 18 years ago

I removed the suggested patch.

Actions

Also available in: Atom PDF