[Typo3-dev] RFC: TYPO3, Kickstarter and M-M database relations

[Peter Niederlag]

Hi,

Mathias Schreiber [wmdb] schrieb:
> Peter Niederlag wrote:
> 
>> Top prio would be imho to assure that any new tables, fields introduced
>> are using true MM-relations. That is my main concern.
>>
>> Second prio should be a good analysis if there is a need or wish to
>> change old structure to new design in Version 5.
>>
>> To strengthen the point again:
>> Imho we should change Kickstarter's default-behaviour *now* (read: as
>> soon as possible) and take any other measures any time later.
> 
> 
> Do you plan a structure like this:
> pages
> be_users
> mm_pages_beusers
> 
> for each relation or do you plan something like one big mm table for all
> relations?

IMHO it might be too early now to pin down a solution.
But this ^^ approach can be handled already pretty good by TYPO3-core imho.

> t3_mm
> -----------------------------------------------------
> |mm_field_1|mm_field_2|mm_table_1|mm_table_2|sorting|
> -----------------------------------------------------
> 
> I have to admin that personally I like databases with less tables better.
> Indexing should work with the "single-table-config".

>From the feedback I think there are a bunch of people that like to see
TYPO3 follow the guidelines of well known DB-Design matters.

> You keep "sorting" in mind?

As said, it might be to early now to talk about any changes that we want
to see in Version 5.

Right now I think we got some awareness for the problem, and also some
good points, *why* it is quite important in the long-time.

So, go for true M-M with anything newly introduced and change default of
Kickstarter *now*.

Everything else we will see when time is appropriate.

My 2 cents,
Peter
-- 
Peter Niederlag
http://www.niekom.de * TYPO3 & EDV Dienstleistungen *
http://www.typo3partner.net * professional services network *