[TYPO3-core] RFC: #11438: Add a registry to t3lib
Oliver Hader
oliver at typo3.org
Mon Aug 31 11:51:57 CEST 2009
Hi Ernesto,
Ernesto Baschny [cron IT] schrieb:
> Each has its pros and cons:
>
> 1)
> pro: can be done without any other core change and no DBAL penalty.
> con: this table probably doesn't need to be InnoDB
>
> 2)
> pro: most clean solution, in my eyes.
> con: probably change required in our SQL-parsing engine (Install Tool)
> and also probably DBAL considerations (stripping this part for non-MySQL
> databases)
>
> 3)
> pro: it works
> con: ugly hack and also needs DBAL considerations which we have had in
> the past (other DB engines doesn't seem to like this kind of key)
>
> I would choose 2) and then seeing if this can already be done already or
> what have to be changed in the SQL-parsing or DBAL-layer to make it
> possible.
Or 4)
... entry_key varchar(128) DEFAULT '' NOT NULL, ...
I'm not sure if someone will really use a 255 character key or use a key
that is longer than 128 characters (and fills together with the
namespace the display in someones IDE from left to right). Thus, 128
chars for the entry_key should be enough.
Besides that I don't think that these large keys add much performance on
excuting SQL queries...
olly
--
Oliver Hader
TYPO3 Release Manager 4.3
More information about the TYPO3-team-core
mailing list