[TYPO3-team-templavoila] RFC: #12257: localizable title fields

[Jigal van Hemert]

Xavier Perseguers wrote:
>> - Change tx_templavoila_tmplobj.title &
>> tx_templavoila_datastructure.title to TEXT
> As DBAL leader, I'm against a change from varchar(100) to text. Text 
> support is a calamity with Oracle and I really don't see the point to 
> change that to text. Increase its size to 200, 500, 1000 or 4000 but do 
> not use a column type that will be mapped to some *LOB in Oracle.

While TEXT seems to be an overkill for a title field, I can't help but 
reaching the conclusion that DBAL compatibility is preventing TYPO3 from 
effeciently using the MySQL database.

- FIND_IN_SET(32, csv_column) must be (csv_column = 32 OR csv_column 
LIKE '32,%' OR csv_column LIKE '%,32,%' OR csv_column LIKE '%,32')
- you can't use text_column = ''
- why not define crdate TIMESTAMP DEFAULT CURRENT_TIMESTAMP ?
- why not define tstamp TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE 
CURRENT_TIMESTAMP ?
- can I use DATETIME columns for a wider range of "timestamps"?
- full text indexes

Maybe it's worth discussing the viability of DBAL in another list and 
another thread.

I'm not pro-MySQL and against-anything-else, but the way DBAL is set up 
only allows you to use features which are supported by all database 
systems which DBAL wants to support.

Sorry for this post and the rant, but this was the umphtiest time that I 
read that something should not be done for the sake of DBAL 
compatibility. In my mind a DBAL should offer features and not impose 
limitations.

-- 
Jigal van Hemert.