[TYPO3-english] static_info_tables data is not fully imported

Xavier Perseguers xavier.perseguers at typo3.org
Fri Mar 11 13:08:25 CET 2011


Hi,

Seems that my answer got lost somewhere...

> * Is it OK to have CREATE scripts for the same (static) tables in two
> files in the extension? It seems to me that this scripts should be only
> in ext_tables_static. In ext_tables should be only one script for
> tx_staticinfotables_hotlist table. Is it correct?

This is the way it should be if you read the meaning of those SQL files 
in Core documentation:

http://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.3.0/view/2/1/#id2343687

> * 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.

 > * 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).

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org



More information about the TYPO3-english mailing list