[TYPO3-english] static_info_tables data is not fully imported

Boris Gulay boris at boressoft.ru
Fri Mar 11 13:38:55 CET 2011


11.03.2011 15:08, Xavier Perseguers пишет:
> Hi,
>
> Seems that my answer got lost somewhere...
Thank you for the answer.

>> * Why DROP TABLE scripts from ext_tables_static are not executed during
>> extension installation process? I can see this statement in
>> class.em_index.php:5403 but it does not actually executed.
>
> You may have found some bug, I don't know. You should investigate a bit
> more and see why it is not executed, perhaps you missed some condition.
OK, I will do it.

>
>  > * Why author of the extension uses UNIQUE keys in addition to
>  > PRIMARY? MySQL does not allow duplicate values in primary key
>  > columns, PostgreSQL too.
>
> In fact, if they have UNIQUE key in addition to PRIMARY then it's not
> needed but maybe they want some other column to be UNIQUE without being
> a primary key because if a column is a primary key, then you have a
> primary key over multiple columns which I never saw in the TYPO3 world
> and relatively seldom in real-world applications even if in some more
> academical context, having a primary key over multiple columns makes
> sense while adding a non-sense auto-increment counter column for tables
> not having "real" primary keys is not. In TYPO3 we have the uid for each
> and every table (except join tables but there the primary key is exactly
> this combination of local and foreign keys).
No. In Sql files there are only one PRIMARY KEY column and to the same 
column UNIQUE index is applied. I will send a message to maintainer of 
this extension with a request to remove this unneeded indexes.


More information about the TYPO3-english mailing list