[TYPO3-dev] TYPO3 on PostgreSQL experiances

[ries van Twisk]

On Mar 27, 2008, at 4:19 AM, Dmitry Dulepov [typo3] wrote:

> ries van Twisk wrote:
>> As promised my experience to installed TYPO3 on PostgreSQL.
>>
>> <snip>
>>
>> Since InnoDB is vendor specific, I have to remove these entries,  
>> and can
>> only be done from command line or using 'some' tool. So I remove the
>> InnoDB  declaration.
>
> I think DBAL should handle it. But we cannot remove it from core  
> files because it gives huge performance improvement in MySQL, which  
> is our default database.

DBAL should handle this indeed for this situation, although I also  
feel that we should ship vendor transparent SQL's much like what the  
idea of DBAL was/is mean

>
>
>> After that I get this message:
>>
>> Warning: Invalid argument supplied for foreach() in
>> /Users/rvt/Sites/typo3_src-4.1.6/typo3/sysext/adodb/adodb/adodb- 
>> datadict.inc.php
>> on line 266
>
> Something ADO/DBAL related again...

It's ADOdb, ADo can be found here : http://www.adodenhaag.nl/adodenhaag/nl/html/algemeen/home/home.pshe
(sorry... had to do it..... :) )

>
>
>> After a other reload... I don't get that message anymore, so I am not
>> sure what's the cause...
>
> Because now you get cached copy of the page.

I never knew that the install tool had a concept of caching.....  
Remember I am in the install tool here

>
>
>> Warning: Invalid argument supplied for foreach() in
>> /Users/rvt/Sites/typo3_src-4.1.6/typo3/sysext/dbal/ 
>> class.ux_t3lib_db.php
>> on line 968
>
> DBAL bug...

Or is it the effect we see of 'something else'?? The fact that PHP  
throws a error there doesn't mean it's the cause.

>
>
>>
>> Warning: Cannot modify header information - headers already sent by
>> (output started at
>
> All "Cannot modify header..." messages can be ignored. They appear  
> because of previous errors and will disappear with them.

This does belong to the above message.....

>
>
>> Installing tt_news brings me:
>>
>> The running TYPO3 version (4.1.6) is higher than allowed (3.8.1)
>
> I afraid you are using some ancient tt_news version.

No, TER gives me a old version... read below

>
>
>> This is interesting because an 2.5.2 is available on TER, however  
>> 2.2.24
>> was installed..
>
> ...which confirms my statement above. Update your extension list.
No, TER gives me a old version... read below


@ Dmitry,

I am not sure... why you did it but you didn't finish my mail and cut  
it off (<snip>)
updating the extension list doesn't help ofcourse if you would have  
readed further where I said:

---------
As a side note...
One suggestion I would like to make is remove the reviewed extensions
option in TER and just show the latest versions.
The reason I say this is because this is a security risk, TYPO3 offers
old software that might be prone to SQL injects, X-Scripting and what
not.
To not Enable extensions without review (basic security check) is
quite misleading for new people.
----------

It's the review check that you need to turn off, currently TYPO3 is  
suggesting old extensions and will always do untill you flip the  
checkbox.


Ries