[TYPO3-dev] the core's missing dbal/postgresql compatibility

[Steffen Kamper]

Martin Kutschker schrieb:
> Michael Greiner schrieb:
>> It would be very kind of you, if you could help me understand the
>> problems and finding solutions.
> 
> All of the EM's problems are due to the fact that it does a string
> comparison of ext_tables.sql lines and the output of DESCRIBE table. It
> does a bit of processing to cope with a few variants in "spelling" and
> order but that's it.
> 
> DBAL doesn't extend the definition parsing in a way that it can deal
> with it.
> 
> Solutions are either to move away from string comparison to a feature
> comparison or to teach DBAL to return table definitions in Mysql style.
> 
> As for the ENGINE property, I think this should be rather easy to
> implement for DBAL. It simply can be ignored (as eg charset/collation
> settings on a per table basis).
> 
> Masi
> 
> PS: It would be a good start for DB compatibility if TYPO3 would run on
> Mysql 5.0 in strict mode which it doesn't. I tried to do it but if fails
> on many occasions due to sloppy practices that were allowed in Mysql.

Hi Masi,

doesn't EM instances t3lib_install for such comparisons?

So imho DBAL should xclass this for the functions 
getFieldDefinitions_fileContent, 
getFieldDefinitions_sqlContent_parseTypes, getFieldDefinitions_database etc

vg Steffen