TYPO3 Core

Hi Kari, thanks for the bugreport, I'll assign the bug to Karsten.

Please try to set up with a completely blank database, no tables in it. The set up with DBAL in place. Running DBAL on an existing database will most likely fail.

Also have a look at bug #2106 for more info.

Also, please provide details about "tried to install dbal": what did you do, how did you configure it in localconf.php, ...

Do You mean that I have to make a new installation without any database.
I'm normally doing new site using 1-2-3.
OK, I have to read a little documentation how I manage to do that, it might take few days but we are not in a hurry. ;-)
----------------------------------------
It's called a try when You fail otherwise it's called a success. I'm going to give a very detailed log how I installed and what I did before I "tried" to install Dbal. When I' m going to install RC2 again, see above.
---------------------------------------
"b) tried to install dbal which caused, " means after I had pushed the button 'Install extension'
---------------------------------------
I looked 0002106, do You think it helps me to find the problem and fix it ?

OK. I used Your advices from 7072.
I deleted whole installation and made a new, only a database without any tables.
I set some normal features in the install tool related to graphics. And I set the compability to rc2.
When I want to log in to backend, I cannot log in and I get error messages,
Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php on line 801

Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php on line 801

Warning: Cannot modify header information - headers already sent by (output started at /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php:801) in /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_userauth.php on line 311

Warning: Cannot modify header information - headers already sent by (output started at /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php:801) in /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_userauth.php on line 312

Warning: Cannot modify header information - headers already sent by (output started at /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php:801) in /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_userauth.php on line 313

Warning: Cannot modify header information - headers already sent by (output started at /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php:801) in /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_userauth.php on line 314

Warning: Cannot modify header information - headers already sent by (output started at /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php:801) in /home/4.0RC2/typo3_src-4.0rc2/typo3/template.php on line 613

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/4.0RC2/typo3_src-4.0rc2/t3lib/class.t3lib_db.php:801) in /home/4.0RC2/typo3_src-4.0rc2/typo3/index.php on line 240

This is self evident due the usernames and passwords are normally in the database !
I don't know why You wanted me to do this spend time ?

After that I used Install tool Database analyzer -> Update required tables COMPARE and installed those tables it suggested. Created an admin user & password. And logged in to the backend.
Steps in the backend:
1) The Reference Index table is empty which is likely to be the case because you just upgraded your TYPO3 source. Please go to Tools>DB Check and update the reference index. -> completed.
2) I changed to EM -> Install extensions. And installed ADOdb. No messages, obviously everything is OK.
3) Installed dbal. DATABASE NEEDS TO BE UPDATED -> make updates. No messages.

4) I logged out and logged in to the backend. Quite funny but the reference index table had to update again.
5) Then I wanted to do a page (main page to start a site) and I got an error message,
Errors:
2: SQL error: 'Column 'TSconfig' cannot be null' (pages:NEW442827ea4baa1)

So what shall we do. I can see the error (from the message above) but this is not my extension and I've spent now quite much time which I could have used to Joo......

The problem is that my MySql is 3.23.x and it should be 4.x also PostgreSQL was not activated in the server. So the problem was in my servers. I think (not sure) that AdoDB needs also MySQL 4.x

BUT:
1) both extensions should check version of the MySQL or that some other db has the prerequisites of this extension and then deny to be installed if the conditions are not satisfied ! The dbal extension is in sysext and is present in every installation. There is users who cannot understand this prerequisites of MySQL or other databases and thus they will cause a lot of harm to them self.

From my part case is closed.

Hi Kari, thanks for your info - I'm sorry that you spent more time than needed because we misunderstood each other. When I said you should try with an empty database, I meant you should create the tables with DBAL already installed - not try to login without the tables, of course.

Anyway, if the first part of the bug is solved by using MySQL 4 that's fine - I'll look into adding a check for that as minimum version.

I am closing this, as the first part is solved according to submitter and the error about TSconfig not allowed to be null has it's own entry as bug #3017.