[TYPO3-dev] TYPO3 on PostgreSQL experiances

[Dmitry Dulepov [typo3]]

ries van Twisk wrote:
> 
> 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

I may be wrong but I think idea of DBAL was to enable using other databases with TYPO3. It means that queries must be converted to the format of corresponding database from MySQL syntax.

>> 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

Ah, sorry... May XML schema in ADODB is used when you create/update tables. I think it ran once and this was when you saw errors.

>>> 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.

Look where it is! sysext/dbal/class.ux_t3lib_db.php.

> 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.

Well, this was discussed, I was in favor of unchecking this box by default but it was banned by many others.

May be I did not read your mail carefully enough (sorry), I assumed you have this checkbox unchecked. This is the very first thing I always do... There is no *any* sense in this checkbox now.

-- 
Dmitry Dulepov
TYPO3 core team
Web: http://typo3bloke.net/
Skype: callto:liels_bugs
"Nothing is impossible. There are only limits to our knowledge"