TYPO3 Core

For tables/fields this can be worked around by setting up a name mapping. For indexes this isn't possible currently.

For automatically created names like index names (or sequences and constarints?) DBAL could use the base name of the table concatenated with the md5 hash of the index name (truncated to the max name length).

Mapping should not be necessary for generated names.

DBAL should provide means to do some kind of auto-mapping. Doesn't ADOdb know about length restrictions?

I looked around, but ADOdb has no support for handling field name length issues (semi-)automatically.

First "attempt" with attached patch.

Long time since I tried Oracle or MSSQL so I cannot stay, but I would expect the problem to still be there since:

1. It cannot obviously fix itself and virtually nobody is actively testing on anything else than MySQL
2. Install Tool has been completely rewritten in 6.2 and the "hook" I introduced is likely NOT to work anymore
3. Extbase is used more and more but is really not good at working with other DBMS

This is still an issue, as you have to set the mappings in LocalConfiguration before starting the installation. With the patch that handles large IN lists I created a base to tackle further DBMS specific issues. But this is a very tough one, as you can catch the processed table and its length, but how do we proceed then?

• Throw an exception that says "Table length is not compliant to your used DBMS" (e.g. 30 in Oracle)? This won't got into 6.2.
• Generate a random table name as defined by more random rules (e.g. replace "extbase" with "xtb", "pages" with "pg" and so on).

Also, this issue occurs with indeces, sometimes they exceed the limit, too.