[TYPO3-core] RFC: Fix sys_refindex problem when using multiplyDBfieldSize=2

Martin Kutschker martin.kutschker-n0spam at no5pam-blackbox.net
Fri Nov 3 22:27:49 CET 2006


Dmitry Dulepov schrieb:
> Hi!
> 
> Martin Kutschker wrote:
>> Maybe we should simply drop multiplyDBfieldSize and require a DB with 
>> proper UTF8 support.
> 
> This is typo3 requirement change: drop of mysql 3.23 (which I am +1), 
> however it will break several my old sites (which I am -1000)...

Hm, a more complicated fix is to check whether the DB is in UTF( or not. 
Depending on this setting TYPO3 could either try to autoadjust the keys 
(perhaps with an emebedded SQL comment as hint?) or it could ignore any 
length constraints in indices.

Currently it breaks the Core in sys_refindex and one of real url's tables.

I did a research on indices on expressions:

Oracle (since 8g)
PostgreSQL (at least since 7.4)
Firebird (since 2.0)

MS SQL Server 2000 supports it via computed columns. So in this case 
DBAL has to create a "shadow column" with the length restriction to use 
it in the index.

But AFAIK ADOdb does not know about such index types, so we would have 
to add support for it.

Hm, the easiest would be to remove multiplyDBfieldSize and require a 
real multibyte capable DB for multiybyte charsets (UTF8, big5, etc) and 
to forbid Mysql col(<length>) indices.

Masi



More information about the TYPO3-team-core mailing list