Bug #11749

to long database tablenames

Added by Alexander Wende over 4 years ago. Updated over 4 years ago.

Status:Closed Start date:2010-12-27
Priority:Should have Due date:
Assigned To:Karsten Dambekalns % Done:

0%
Category:Persistence
Target version:TYPO3 Flow Base Distribution - 1.0 beta 1
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

Hi,
I work in some projects with extbase and now I have a problem with the Flow3 conversion - so I post it in the Flow3 bugtracker.
In one of the projects I work with a complex domainmodell with many objects.
The objects are named in german because it doesn't make sense to translate technicals terms.
In some cases the name of the mysql tables is too long. MySQL tablenames haves a limitation of 64 characters. But this is not only a MySQL problem. Oracle tablenames has to be shorter then 31 characters.
Because of the flow3 conversion of tablenames this is a generell problem. But if flow3 should be indepentend of the uses database this problem should be solved. With extbase I change the mapping manual, but that's not very nice.
A simple solution would be to use a hash value instead of the name of the model to create database tablenames. The disadvantage would be that the clearness get lost.

Greetings
Alex

History

#1 Updated by Karsten Dambekalns over 4 years ago

  • Category set to Persistence
  • Status changed from New to Closed
  • Assigned To set to Karsten Dambekalns

In the generic persistence layer of FLOW3 only four tables are ever used (entities, properties, properties_data, valueobjects).

For the Doctrine 2 persistence custom table names are possible with the name attribute of the Entity annotation.

#2 Updated by Karsten Dambekalns over 4 years ago

  • Target version set to 1.0 beta 1

Also available in: Atom PDF