Bug #14422

bug with MySQL 4.1.7

Added by old_kttxpo over 10 years ago. Updated almost 9 years ago.

Status:Closed Start date:2004-11-30
Priority:Should have Due date:
Assigned To:Michael Stucki % Done:

0%

Category:Install Tool Spent time: -
Target version:-
TYPO3 Version:3.7.0 Is Regression:
PHP Version: Sprint Focus:
Complexity:

Description

all SQL statements like NOT NULL DEFAULT '0' seem to be rejected by mysqld
There has already been some fixes for ext. installation, but if you use the install tool to upgrade from 3.6 to 3.7 for example, you cannot import the static tables, and you cannot apply the comparison's results as well.

Well.. if it has already been fixed up, I'll blush and cry sorry.
(issue imported from #M560)


Related issues

duplicates Core - Bug #14354: MySQL gt 4.1 no default value for auto inc Closed 2004-10-12

History

#1 Updated by old_kttxpo over 10 years ago

looks like # 0000546, because of the new syntax on auto increment.

#2 Updated by old_kttxpo over 10 years ago

someting like this should be able to correct it.
!/bin/bash
version=typo3_src-3.7.0
for i in $(find $version -name *.sql)
do
echo "Patching $i..."
sed -r "s/DEFAULT '0' NOT NULL auto_increment/NOT NULL auto_increment/g" -i $i
grep "DEFAULT '0' NOT NULL auto_increment" $i
done
for i in $(find content/typo3conf -name *.sql)
do
echo "Patching $i..."
sed -r "s/DEFAULT '0' NOT NULL auto_increment/NOT NULL auto_increment/g" -i $i
grep "DEFAULT '0' NOT NULL auto_increment" $i
done

Also available in: Atom PDF